AddUser


Description

Adding user %UserID% to the runtime and build MQSW database

Details
Input data structure AddUser
Output data structure AddUserOK
Belongs to category Administration
Audit Full
Refresh policy Push
Keep process 600 sec
Keep workitems 120 sec
Prompt at process start yes
Creation of return code Last code
Notify duration 600 sec
Administrator ADMIN

Documentation

The AddUser process is intended as a demo of how an internal administrative process to support the business process could be setup. There is a clear need for additional support processes and workflow is clearly a good way to manage them. It can easily be connected to existing applications and co-ordinate there execution and used to track who has performed each task for example such as authorizing changes to the system i.e. adding people to the system. This is just an example. More work would be required to turn this demo into an applicable that could be used in a live environment. Plus changes would be required to meet different business requirements. What happens when you delete someone from the system for example?

Input container initialization:
Name Value
UserID BETH
UserFirstName Beth
UserSecondName Arnold

List of contained activities:

Activity name Activity type incoming control connectors outgoing control connectors
AddUser Block 1 0
UserAlready Program activity 1 1
ValidateUser Program activity 0 1



AddUser (Block)

Description

The block here will attempt to add the user again.

Output container initialization
Name Value
Retry N

Details
Control from UserAlready when _RC = 1
Data from ValidateUser Mappings:
  • _STRUCT maps to _STRUCT
AddUser Mappings:
  • AddUser maps to _STRUCT
Data to AddUser Mappings:
  • AddUser maps to _STRUCT
Sink  Mappings:
  • _STRUCT maps to _STRUCT
Start when at least one incoming connector is true
Exit when Retry = "N"
Input data structure AddUser
Output data structure AddUserOK

Documentation

Block is required in case there is a problem and another request is required. The User details can be update between each request. Retry if set to anything other than "N" the process will loop back into the adduser block.

List of contained activities:

Activity name Activity type incoming control connectors outgoing control connectors
CorrectUserORQuit Program activity 1 0
CreateFDL Program activity 0 1
Erase FDL Program activity 3 0
GoCheckUser Program activity 1 3
Request Stopped Program activity 1 1
RunImport Program activity 1 1
ViewLog Program activity 1 2



CorrectUserORQuit (Program Activity)

Description

%AddUser.UserID% - %AddUser.UserFirstName% %AddUser.UserSecondName%

Input container initialization
Name Value
Retry N

Details
Control from ViewLog
Data from GoCheckUser Mappings:
  • _STRUCT maps to _STRUCT
CorrectUserORQuit Mappings:
  • _STRUCT maps to _STRUCT
Data to CorrectUserORQuit Mappings:
  • _STRUCT maps to _STRUCT
Sink  Mappings:
  • _STRUCT maps to _STRUCT
Start automatic
Start when at least one incoming connector is true
Exit automatic
Priority defined in input container
Staff assignment people
Assigned people AUTO
Referenced programs ValidateUser
Input data structure AddUserOK
Output data structure AddUserOK

Documentation

Change the requested or correct the problem as reported in the Log.


CreateFDL (Program Activity)

Description

FDL for user %UserID%

Details
Control to RunImport
Data from Source  Mappings:
  • _STRUCT maps to _STRUCT
Start automatic
Start when at least one incoming connector is true
Exit automatic
Priority defined in input container
Staff assignment people
Assigned people AUTO
Referenced programs CreateAddUserFDL
Input data structure AddUser
Output data structure AddUser

Documentation

This activity creates an FDL for import to MQSeries Workflow.


Erase FDL (Program Activity)

Description

Deleting the FDL for %FileName%

Details
Control from GoCheckUser
Request Stopped
ViewLog
Data from Source  Mappings:
  • UserID maps to FileName
Start automatic
Start when at least one incoming connector is true
Exit automatic
Priority defined in input container
Staff assignment people
Assigned people AUTO
Referenced programs DelFile
Input data structure FileName
Output data structure Default Data Structure

Documentation

Clean up the work files.


GoCheckUser (Program Activity)

Description

Created? %UserID% - %UserFirstName% %UserSecondName%

Output container initialization
Name Value
Retry N

Details
Control from RunImport
Control to Erase FDL
Request Stopped when _RC = 2
ViewLog when _RC = 1
Data from Source  Mappings:
  • _STRUCT maps to _STRUCT
GoCheckUser Mappings:
  • _STRUCT maps to AddUser
Data to ViewLog Mappings:
  • AddUser.UserID maps to FileName
GoCheckUser Mappings:
  • _STRUCT maps to AddUser
CorrectUserORQuit Mappings:
  • _STRUCT maps to _STRUCT
Request Stopped Mappings:
  • AddUser maps to _STRUCT
Sink  Mappings:
  • _STRUCT maps to _STRUCT
Start automatic
Start when at least one incoming connector is true
Exit automatic
Priority defined in input container
Staff assignment people
Assigned people AUTO
Referenced programs GoCheckUser
Input data structure AddUser
Output data structure AddUserOK


Request Stopped (Program Activity)

Description

User %UserID% already created

Details
Control from GoCheckUser when _RC = 2
Control to Erase FDL
Data from GoCheckUser Mappings:
  • AddUser maps to _STRUCT
Start manual
Start when at least one incoming connector is true
Exit automatic
Priority defined in input container
Staff assignment people
Assigned people AUTO
Referenced programs StopRequest
Input data structure AddUser
Output data structure Default Data Structure

Documentation

This activity reports that the request has been stopped. You can change this activity to attempted to do something more sophisticated like to decide why the request has failed and then try again.


RunImport (Program Activity)

Description

Running Import Job

Details
Control from CreateFDL
Control to GoCheckUser
Data from Source  Mappings:
  • UserID maps to FileName
Start automatic
Start when at least one incoming connector is true
Exit automatic
Priority defined in input container
Staff assignment people
Assigned people AUTO
Referenced programs FMCIBIE
Input data structure FileName
Output data structure Default Data Structure

Documentation

This activity runs the import to MQSeries Workflow


ViewLog (Program Activity)

Description

Log %FileName% - File: %FileName%.log

Details
Control from GoCheckUser when _RC = 1
Control to CorrectUserORQuit
Erase FDL
Data from GoCheckUser Mappings:
  • AddUser.UserID maps to FileName
Start automatic
Start when at least one incoming connector is true
Exit automatic
Priority defined in input container
Staff assignment people
Assigned people AUTO
Referenced programs Notepad
Input data structure FileName
Output data structure Default Data Structure


UserAlready (Program Activity)

Description

Already Exist? %UserID% - %UserFirstName% %UserSecondName%

Output container initialization
Name Value
Retry N

Details
Control from ValidateUser
Control to AddUser when _RC = 1
Data from ValidateUser Mappings:
  • _STRUCT maps to _STRUCT
Data to Sink  Mappings:
  • _STRUCT maps to _STRUCT
Start automatic
Start when at least one incoming connector is true
Exit automatic
Priority defined in input container
Staff assignment people
Assigned people AUTO
Referenced programs GoCheckUser
Input data structure AddUser
Output data structure AddUserOK

Documentation

This activity checks to see if the userid exists in MQSeries Workflow already.


ValidateUser (Program Activity)

Description

%UserID% - %UserFirstName% %UserSecondName%

Input container initialization
Name Value
UserID BETH
UserFirstName Beth
UserSecondName Arnold

Details
Control to UserAlready
Data from Source  Mappings:
  • _STRUCT maps to _STRUCT
ValidateUser Mappings:
  • _STRUCT maps to _STRUCT
Data to ValidateUser Mappings:
  • _STRUCT maps to _STRUCT
AddUser Mappings:
  • _STRUCT maps to _STRUCT
UserAlready Mappings:
  • _STRUCT maps to _STRUCT
Start automatic
Start when at least one incoming connector is true
Exit automatic
Priority defined in input container
Staff assignment process starter
Referenced programs ValidateUser
Input data structure AddUser
Output data structure AddUser

Documentation

This activity in the process gives the opportunity to change the input data from the start of the request. To improve this process another activity could be added before this one to validate the data. It would check to see if the requested USERID is already being used. If the UserID has already be taken then the process would be to return to the requester for a another UserID.