The product enquiry process involves handling enquiries about a product. Product enquiries can be of two types – Product Enhancements and Bugs. The user has to fill up the enquiry details as well as the enquiry option (type). Based on the specified option, the enquiry is directed to the Project Manager or Team Manager. These resources will then handle the enquiry. This topic discusses the flow of actions in the workflow process design.
To view the actions involved in the Workflow defined for the sample Product Enquiry Application
1. Open the Admin Login Page and login to the admin section by selecting the following login name and clicking the Submit button:
username: Daniel@skeltademo.com
2. Go to the Product Enquiry Designer option in the Main Menu.
To access the Product Enquiry Application
1. Click on http://localhost/SkeltaSample/Samples.aspx
This opens the Skelta Sample Applications Main Page.
2. In this page select the Product Enquiry option by clicking the corresponding radio button.
3. Click the Submit button.
Consider a scenario in which a product enquiry is submitted. This will have to be classified according to the enquiry type i.e., Product Enhancements, or Bugs.
If the enquiry is for Product Enhancement, then it will be sent to the Project Manager named Kevin for necessary action, which is to assign a Team Manager to take charge of the enquiry. If Kevin fails to take action within 30 minutes, an alert is sent to the Director. If no action is taken even after 1 hour, an alert is sent to the CEO. If Kevin selects a Team Manager, then the enquiry is sent to this resource, who will then have to designate a Senior Developer to take up the Product Enhancement. If the Team Manager does not take action within 2 hours, then an alert is sent to the Director. If no action is taken for 4 hours then the alert is sent to the CEO. If the Team Manager has selected a Senior Developer, then the enquiry is sent to this resource, who will have to set the status of the enquiry to "Closed" after completing the requested product enhancement. If the status is set to "Pending" then the enquiry is sent back to the developer for action. This is repeated until the resource sets the status to "Closed".
If the enquiry is to report Bugs, then it will be sent to the Team Manager named Philip for necessary action, which is to designate a Senior Developer to fix the bug. If the Team Manager does not take action within 2 hours, then an alert is sent to the Director. If no action is taken for 4 hours then the alert is sent to the CEO. If the Team Manager has selected a Senior Developer, then the enquiry is sent to this resource, who will have to set the status of the enquiry to "Closed" after fixing the reported bug . If the status is set to "Pending" then the enquiry is sent back to the developer for action. This is repeated until the resource sets the status to "Closed".
In the sample application, the workflow process starts when a product enquiry is submitted by the user. On submission the Workflow engine is alerted and the process begins.
Go through the Organization Chart, to understand the hierarchy of resources involved in the Skelta Sample Applications.
To see how the Workflow actions take place, follow the steps given below:
1. Product Enquiry Submission
a. After selecting the Product Enquiry option in the Sample Applications Main Page, click on the Submit button to open the Place Enquiry form.
b. Fill up the Enquiry details in the form.
c. Select the Type of Enquiry (i.e. Production Enhancements or Bugs) using the Enquiry Options radio button.
d. Submit the Enquiry
Note: Click on the View Workflow Submission Code link to view Content Data passed to the workflow (the Content is initialized in the Enquiry Process Designer’s Start Action).
After the submission button is clicked, the Engine is alerted about the enquiry submission, and the enquiry is sent to the Project Manager or Team Manager for action, depending on the enquiry type.
2. Product Enhancement Type Enquiry
If the enquiry type is "Product Enhancements", then the action goes to the Project Manager, who has to select or assign a Team Manager for further action.
a. Select the Product Enquiry option in the Sample Applications Main Page and click Submit.
This opens the Place Enquiry page.
b. In this page, click on Activity List in the Main Menu.
c. Select a user with email ID Kevin@skeltademo.com and click on the Submit button.
The Activity List Control included in this page will show a listing view of the Enquiry submitted, while the Activity UI Control will show the detailed view of a selected Enquiry listing.
d. Clicking on the Ref Id or Workflow will display the list of Team Managers' names in the page. The Project Manager has to select a Resource (A) from this list.
e. The Proceed button has been provided for action to be taken by the Project Manager.
Now, the selected resource (A) will handle the subsequent actions.
f. If the Project Manager does not take any action for 30 minutes, then an alert message will be sent to the Director. If after one hour the Project Manager has still not taken action, an alert is sent to the CEO.
g. Logout from the Activity List page.
h. Click on the Product Enquiry option in the Main Menu. In the Place Enquiry page that opens, click on the Activity List link in the Main Menu.
i. Select resource (A)’s email ID from the list and click on the Submit button.
The Activity List Control included in this page will show a listing view of the enquiry submitted and the Activity UI Control will show the detailed view of a selected enquiry listing.
j. Clicking on the Ref Id or Workflow will give the list of Senior Developers’ names in the page. The Team Manager has to select a Resource (B) from this list.
k. The Proceed button has been provided for action to be taken by the Team Manager.
Now, the selected resource (B) will handle the subsequent actions.
l. If the Team Manager does not take any action for 2 hours, then an alert message will be sent to the Director, and if the manager does not take action for 4 hours an alert is sent to the CEO.
m. Click on the Product Enquiry option in the Main Menu. In the Place Enquiry page that opens, click on the Activity List link in the Main Menu.
n. Select resource (B)’s email ID from the list and click on the Submit button.
The Activity List Control included in this page will show a listing view of the enquiry submitted and the Activity UI Control will show the detailed view of a selected enquiry listing.
o. Clicking on the Ref Id or Workflow will display the Checklist questions and possible answers for the enquiry.
p. If the selected status is "Closed", then the Enquiry database is updated with "Closed" status.
q. If the selected status is "Pending", then the Enquiry database is updated with "Pending" status and the activity is sent to this Resource (B) once again. The Checklist is sent to the Resource (B) until he/she sets the enquiry status to "Closed".
r. If the Resource (B) does not take any action for 4 hours, then an alert message is sent to the Director, and if resource (B) does not take action for 6 hours an alert is sent to the CEO.
s. Alert messages are sent to the CEO every 6 hours to take action on the enquiry.
t. Logout from the session.
3. Bugs Enquiry
If Enquiry type is "Bugs", then it goes to the Team Manager, who has to select or assign a Senior Developer for further action.
a. Select the Product Enquiry option in the first page and click Submit.
This opens the Place Enquiry page.
b. In this page, click on Activity List in the Main Menu.
c. Select a user with email ID Philip@skeltademo.com and click on the Submit button.
The Activity List Control included in this page will show a listing view of the Enquiry submitted to the resource currently logged in, while the Activity UI Control will show the detailed view of a selected Enquiry listing.
d. Clicking on the Ref Id or Workflow will display the list of Senior Developers’ names in the page. The Team Manager has to select a Resource(C) from this list.
e. The Proceed button has been provided for action to be taken by the Team Manager.
Now, the selected resource (C) will handle the subsequent actions.
f. If the Team Manager does not take any action for 2 hours, then an alert message will be sent to the Director. If after 4 hours the Team Manager has still not taken action, an alert is sent to the CEO.
g. Logout from the Activity List page.
h. Click on the Product Enquiry option in the Main Menu. In the Place Enquiry page that opens, click on the Activity List link in the Main Menu.
i. Select resource (C)’s email ID from the list and click on the Submit button.
The Activity List Control included in this page will show a listing view of the enquiry submitted and the Activity UI Control will show the detailed view of a selected enquiry listing.
j. Clicking on the Ref Id or Workflow will display the Checklist questions and possible answers for the enquiry.
k. If the selected status is "Closed", then the Enquiry database is updated with "Closed" status.
l. If the selected status is "Pending", then the Enquiry database is updated with "Pending" status and the activity is sent to the Senior Developer once again. The Checklist is sent to the Senior Developer until he/she sets the enquiry status to "Closed".
m. If the Senior Developer, i.e., Resource (C) does not take any action for 4 hours, then an alert message is sent to the Director, and if resource (C) does not take action for 6 hours an alert is sent to the CEO.
n. Alert messages are sent to the CEO every 6 hours to take action on the enquiry.
o. Logout from the Session.