A typical simplified workflow for an Interaction life cycle is illustrated in the following figure:
Step 1: Design/Update Interaction
Using the Interaction Designer, a designer creates a new Interaction, or modifies an existing one based on feedback from colleagues, administrators, and/or other reviewers.
Step 2: Publish to the Interaction Server
The designer publishes the Interaction to a specific account on the web server. The Interaction is assigned a status of Draft, and is listed on the Interactions page of the relevant account.
When an updated version of an Interaction is published, the new version automatically overwrites the previous version. The new version number is assigned transparently by the system.
Steps 3 & 4: Test/Approve the Interaction
Administrators run the Interaction from the server for reviewing and testing purposes. If necessary, the designer modifies the Interaction (in the Interaction Designer), and republishes it to the server.
When the Interaction is approved by administrators, the status of the Interaction is changed from Draft to Approved. Only one published version of an Interaction can have an Approved status.
Step 5: Analyze Interaction Use
After an Interaction has been in use for some time, reports can be generated and reviewed. These reports show patterns of actual Interaction element flow and real time measurements of Interaction workflows. If the reports reflect a need for improvement (e.g., the time spent on a certain Interaction element is longer than expected), change requests can be sent back to the designer. After the Interaction is edited (in the Designer), it is republished, tested and approved.