A condition matches document type attributes against decision points and routes the documents to different paths based on the specified attribute and value combinations. The document type attributes against which conditions can be created are predefined in Sterling Selling and Fulfillment Foundation. You can use these attributes in any combination or you can create conditions that run the appropriate application logic for specific circumstances.
For more information about Conditions, see the Organization and participant modeling concepts.
To view the condition repository details for Task Management:
For more information about creating and modifying Conditions, see the Organization and participant modeling concepts.
The default transaction repository does not have any conditions specified.