Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 5 Current »

Expand the work flow to display individual work flow details.

The work flow details are where everything comes together: statuses, action types, etc.

Multiple work flows (and therefore work flow details) can be specified for various levels.


Click New Work Flow Detail to create a work flow detail. Click Edit to edit a work flow detail.


 General

FIELDDESCRIPTION
SequenceThe sequence of this detail in the work flow.
Button NameThe name on the button that is visible when the work flow detail is triggered.
Success/Failure AlertThe desired success and/or failure alert(s).
Alert Only Contributors

Controls whether alerts are sent exclusively to users who have interacted with the transaction or all users subscribed to the alert with access to the trading partner.

This toggle button is hidden until a success or failure alert is selected, and it defaults to "off."

 Notes and Reason Codes

FIELDDESCRIPTION
NoteControls whether a note is required when the work flow detail is executed.
Reason CodeControls whether a reason code is required when the work flow detail is executed.
Reason Code CategoryControls which reason codes are available for selection.
 Status

FIELDDESCRIPTION
Result StatusThe detail status.
Status Low RangeThe lower limit for the work flow detail.
High The upper limit for the work flow detail.
 Transaction Config

FIELDDESCRIPTION
CodeThe code (or name) for the work flow detail.
DescriptionDetailed description.
Validate from UIControls whether the work flow detail can be validated from the UI.
ValidationThe validation system action. If no validation is desired, select DoNothingValidation.
ProcessThe process system action. If no system processing is desired, select DoNothingProcessing.
Child Transaction TypeThe business transaction type for the child of the work flow detail. This is useful for situations where an action on the parent business transaction causes a change to any related children.
System KeyThe system key. System keys are used to control UI functionality.
 Technical

FIELDDESCRIPTION
Method

Controls how the action behaves:

  • Action: Does not prompt the user.
  • Modal: Requires more interaction.
RequiredControls whether this step is required to move to a closed status.
Auto FireControls whether this step automatically processes if the previous step completes successfully,
Decrement StatusControls whether the action can lower the status (move the status backward). It is possible to set up a status that should not go backward.
Allow Simple TransactionApplies to PO flow.
  • No labels