General tab

The General tab has these sections:

  • Email Connection Information

    In this section, you can select the connection configuration that will be used for notification and reminder messages.

  • Work Assignment

    You can assign tasks and/or users to an action in the Work Assignment section.

  • Actions

    You can specify the actions that the tasks or users will be performing in the Actions section.

Assigning tasks and users to a work assignment

When configuring a work assignment, you are answering the question, who needs to take the actions?

Before you start, if you will assign a task to a User Action, the task must already exist.

  1. On the User Action node, go to the Properties > General tab.

  2. In the Work assignment section, click the Add button to open the Select tasks and/or users dialog box.

  3. On the Tasks tab, select tasks.

    All users who are assigned the tasks that you selected will be assigned to the User Action you are creating.

    On the Task variable list (CSV), you can use variables to specify tasks. These are either process variables that you declared in the Start node or any variables that will be passed to the process.

    For example, if you have created a process variable called "IT_Mgr," can could specify <!IT_Mgr>.

    Separate multiple variables with commas. For example, if you have created two process variables, "IT_Mgr" and "IT_Director," specify <!IT_Mgr,!IT_Director> for both variables.

    You can reference a global service variable passed by a workunit and set up a query to locate the task or user who should be assigned the action.

    Note: 

    • If a variable is defined in the Start node, the value of the variable is saved after User Action and Wait node.

    • If a variable is defined in the Assign node, the value of the variable is not saved after User Action and Wait node.

    • If a variable is defined in the Start node but is changed in the Assign node, the value of the variable is retained after User Action and Wait node.

    User Action and Wait nodes bring down the processing of a workunit and results to local, or non-global, variables not being saved.

  4. Click the Users tab.

  5. On the Users tab, select the users who should be assigned this User Action.

    On the User variable list (CSV), you can use variables to specify users. These are either process variables that you declared in the Start node or any variables that will be passed to the process.

  6. Click OK.

Note: 

You can assign a User Action to a task that does not have any users assigned. If this workunit is triggered, its action state will be pending until a user is assigned to the selected task.

Configuring actions for users or tasks

When configuring an action, you are answering the question, what actions need to be taken?

  1. On the User Action node, go to the Properties > General tab.

  2. In the Actions section, click the Add button to open the Action Builder dialog box.

  3. Specify this information:

    Action name

    Specify a name for the action.

    Execute command
    Note: This is for application development use only. See Using the Execute command for details.
    Show reason code pop up

    Select this option to show a reason code form in a pop-up window. When this option is selected, a reason form is displayed when taking an action. A pop-up window is displayed in the Inbasket while approving work.

    Reason code required

    This field is only enabled when the Show reason pop up field is selected.

    Select this option to require approvers to specify a reason code. If this option is not selected, the Reason Code field will be optional.

    The reason code is a grouping or phrase that indicates the reason for the action.

    Reason comment required

    This field is only enabled when the Show reason pop up field is selected.

    Select this option to require approvers to specify an action comment. If the Reason comment required field is not selected, the Reason Comment/Message fields will be optional.

    The reason comment is a message that explains why the action was taken.

    Reason subject

    This field is only enabled when the Show reason pop up field is selected.

    Reason codes are associated with subjects. For example, a subject such as ContractApproval can be associated with Verified Contract and Checked Background reason codes.

    If you the Show reason code pop up is selected, you must select a reason subject.

    To set up a subject and assign reason codes to a subject, follow these general steps:

    1. Add subjects to prodline.lpl in $LASRCDIR\<dataArea> or in Configuration Console.

      See "Adding Business Subjects for a Data Area" in the Configuration Console User Guide.

      Note: 

      You must have the GlobalUIConfigAccess_ST security class assigned to your user to access the Configuration Console.

    2. Access Process Server Administrator and select Configuration > Reason Code > Action Reason. In this page, you can add new reason codes and assign them to your subjects.

  4. Click OK.

Using the Execute command

The Execute command field is reserved for use by Infor-delivered applications and process flows. This field serves two purposes:
  1. To prevent the form or record the user is currently on from being updated after the user takes the action.

    To prevent the form or record the user is on from being updated, specify the value of the Execute command field to update=false. This is not case-sensitive; therefore, values such as Update=false are also handled correctly. The Process Automation action will still be taken, and the work unit will proceed, but the form or record displayed will not be updated.

  2. To inhibit the availability of some actions. For example, they optionally would not be displayed on the user interface.

    To restrict the availability of some actions, that is, to prevent certain action buttons from being displayed in the user interface, specify this in the Execute command field using this format: BusClassName.InstanceActionName

    If the user lacks security access to the LPL action on the specified business class, the action will be unavailable, and the corresponding action button will not be displayed on the user interface.

The Execute command is used when the Display type on the Display Desktop tab on the User Action node is set to Landmark URL. Most often, the Landmark URL field is set to <!_folders.folder[0]>, automatically populated when the work unit is triggered through the appropriate LPL, containing the URL for the relevant LPL navigation.

An example of the LPL to trigger a work unit is:

Example is an Instance Action
  Action Rules
    initiate Example process
        title is "Example"
        URLs // Note: The generated URL is put into the _folders array on the work unit
          "<linkback(webapp is <web-app-name> navigation is <LPL-navigation-name> text
          is \"<user-friendly-name>\" session key <business-class> is \"<key>\")>"
Note: The Execute command is intended for use only in Infor-delivered applications and process flows. While customers are not prohibited from using this feature, it is not officially supported by Infor.