Difference between revisions of "Create Consumer Provider link using Workflow Task - Why?"

From SmartWiki
Jump to: navigation, search
 
(7 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{Under Construction}}
 
 
{{WhyHeader}}
 
{{WhyHeader}}
  
  
  
SmartSimple's UTA '''[[Configuring UTA Provider/Receiver (Consumer) Relationships|Provider/Consumer Relationships]]''' allows for the sharing of data between different [[UTA|UTAs]].The UTA providing the data (the source UTA) is referred to as the '''Provider''' while the UTA receiving the data is referred to as the '''Consumer'''.
+
This feature allows the creation of a Consumer / Provider relationship using the Workflow subsystem and eliminates the need for custom scripting.
 +
SmartSimple's UTA '''[[Configuring UTA Provider/Receiver (Consumer) Relationships|Provider/Consumer Relationships]]''' allows for the sharing of data between different [[UTA|UTAs]]. The UTA providing the data (the source UTA) is referred to as the '''Provider''' while the UTA receiving the data is referred to as the '''Consumer'''.  
  
 +
Example scenario: A Level 1 application is submitted and you would like to link it to the Budget Level 2. This link would be based on on criteria such as call settings to Level 1 type etc. The workflow task would allow the use of variable syntax to get the ID (or IDs) of the provider or consumer.
  
An example of when we would like to use this is for the new Budget Allocation Manager. i.e. When a level 1 application is submitted we would like to link it to the Budget Level two. This link would be based on on criteria such as call settings to Level One type etc. The workflow task would allow us to use a variable syntax to get the ID (or IDs) of the provider or consumer. We could also specify what the role should be.
+
==Notes==
 
+
* This feature is only available to '''Level 1''' and '''Level 2''' workflows.
 
 
 
 
* This feature is only available to level 1 and level 2 workflows.
 
* Separate Object ID / Variables by semicolon (For example: @#2762780#@;@#2762781#@).
 
 
 
* From the '''Task Type''' field, options to create both a '''Consumer / Provider link''' as well as a '''Provider / Consumer link''' are available.
 
  
  
Line 23: Line 18:
 
|}
 
|}
  
 
+
==See Also==
[[Category:Under Construction]]
+
[[Workflows - Overview]]<br />
 +
[[Workflow Task Types]]<br />
 +
[[Task Types Available to Workflow Types]]<br />
 +
[[Workflow Types]]<br />
 +
[[Category:Consumer/Provider]][[Category:Consumer/Provider]]

Latest revision as of 09:30, 1 September 2016

Why.jpeg This article will explain why this feature is a benefit to your organization.


This feature allows the creation of a Consumer / Provider relationship using the Workflow subsystem and eliminates the need for custom scripting. SmartSimple's UTA Provider/Consumer Relationships allows for the sharing of data between different UTAs. The UTA providing the data (the source UTA) is referred to as the Provider while the UTA receiving the data is referred to as the Consumer.

Example scenario: A Level 1 application is submitted and you would like to link it to the Budget Level 2. This link would be based on on criteria such as call settings to Level 1 type etc. The workflow task would allow the use of variable syntax to get the ID (or IDs) of the provider or consumer.

Notes

  • This feature is only available to Level 1 and Level 2 workflows.


How.png Click here for details on how to add this feature to your system.

See Also

Workflows - Overview
Workflow Task Types
Task Types Available to Workflow Types
Workflow Types