Workflow Actions: Configuration of Actions

You can configure workflow actions in the following ways:

Add, update, or delete an action in the screen configuration by calling the Add, Update, or Delete method, respectively, in the WithActions method at the screen configuration level.
For example, see Step 3: Adding the Action to the Workflow of the Workflow Actions: To Implement a Simple Action activity.
Add, update, or delete an action in a specific state of a workflow by calling Add, Update, or Delete method, respectively, in the WithActions method at the state level. By adding an action to a state, you make it available in this state unless it is restricted by the settings specified in the screen configuration.
For details on configuring an action in a workflow state, see Workflow States: Configuration of Actions.
For example, see Workflow States: To Define a Workflow State.
Assign field values when the action is performed by calling the WithFieldAssignments method while adding or updating the action in the screen configuration. For a detailed example, see Workflow Actions: To Implement an Action with Field Assignments.
Provide the parameters of an action by calling the WithParameterAssignments method.
Display a dialog box when an action is clicked by calling the WithForm method. For details on defining dialog boxes, see Workflow Dialog Boxes: General Information.
Configure the appearance of an action on the More menu and form toolbar. For more information, see Workflow Actions: Appearance of Buttons and Commands.
Configure the persisting options. That is, you can specify when the system should save the current changes to the database. For details about persisting options, see Workflow Actions: Persisting Options.
Configure mass processing, as described in Workflow Actions: Mass Processing Actions.
Configure the behavior of an action. For details, see Workflow Actions: Action's Behavior.
Map an action to the MYOB mobile app.
Display an action on a side panel by calling the IsSidePanelScreenmethod, as described in Workflow Actions: Opening of a Side Panel

Levels of Action Configuration

You can configure an action on the following levels, [1]janice.paganiniSame comments I made about fields (I mention this so you can copy whatever solutions you use there): I added this to clarify that these are in an order. But please make this more specific to say what kind of order? Order of precedence? I think it would be clearer if we at least said "in order from the highest to the lowest level" ...2022/09/2722:21:18-04:00which are listed in order:

In the definition of the action in a graph or in one of its extensions
In a screen configuration
In a workflow state

Configurations defined on each level are applied to the subsequent level. For example, if you specified a category for an action in the PXButton attribute in a graph, this category is the default category for this action for the whole screen configuration, and you can change it in the screen configuration. But for some properties (see the table below), the configuration specified on the [2]janice.paganinilevel beneath it?332022/09/2815:23:33-04:00next level can only [3]janice.paganiniWhat does narrow mean in this context? I think it means something like filter, especially with a combo box, and "filter" might be a better choice. But I am not sure what narrowing or filtering would mean for the things like visibility that are either true or false.2022/09/2815:16:33-04:00narrow what has been defined in the [4]janice.paganini"level above it"?662022/09/2815:24:01-04:00previous level.

[5]janice.paganiniWe need to state what the significance of the plus sign is. Can we clarify that? Separately, it is confusing to me that we would use a table when what we are saying is that all three options (or any combination thereof) are possible at all levels. The table is only indicating in the comment column whether all you can do is narrow the value or you can set it ... the other information is superfluous because all levels can be set.2022/09/2815:25:15-04:00

The following table lists all possible configuration types and the levels where they can be changed.


Configuration Type	Graph	Screen Configuration	Workflow State	Comment
Visibility	+	+		The condition on the next level can only [6]janice.paganiniIt is hard to conceptualize what narrowing visibility or availability could mean ...2022/09/2815:27:44-04:00narrow what has been defined in the previous level.
Availability	+	+
Category	+	+		The location inside the category can be specified only in the screen configuration.
Connotation	+		+
Display on the form toolbar	+		+
Assign field values	+	+
Provide parameters		+
Display a workflow dialog box		+
Configure the persisting option	+	+
Run report, open a generic inquiry, create a new record	+	+
Expose the action to the mobile app		+

Mapping a Workflow Action to the Mobile App

You can map a workflow action to the MYOB mobile app without using MSDL. To map a workflow action, call the IsExposedToMobile method while adding an action to a screen configuration.

For this method to work, you must use MSDL to map the screen where the action should be displayed. For more information about mapping forms to the MYOB mobile app, see Mobile Framework Guide.