Exploring Requirement Intake Diagram

Learn about the Requirement Intake Diagram application key features, flow, and workspace.

Requirement Intake Diagram overview

Use Requirement Intake Diagram to design the automation requirements visually. The diagram provides a way to visualize the complete requirements, which depend on different departments and involve multiple activities. Once the diagram is created, it will be translated into a detailed Playbook Experience process, which can then be configured and executed as actual running automation.

Requirement Intake Diagram users

Table 1. Users

Role title	Description	Contains roles
sn_ac.automation_admin playbook.activity_def_read playbook.write connection_admin cmdb_read	Sets up Requirement Intake Diagram application configurations. Performs all the actions in the Requirement Intake Diagram application. Possesses CRUD access for all tables.	sn_ac.automation_business_user sn_ac.automation_technical_user sn_ac.automation_admin
sn_ac.automation_technical_user playbook.activity_def_read playbook.write connection_admin cmdb_read	Creates a requirement diagram, translates it into a Playbook Experience process, and eventually creates the automation.	playbook.write contains pd_shared.user
sn_ac.automation_business_user playbook.activity_def_read playbook.write	Requests for an automation by providing the requirement diagram.	playbook.write contains pd_shared.user

Requirement Intake Diagram flow

The following diagram shows the flow of the Requirement Intake Diagram. Users with sn_ac.automation_business_user, playbook.activity_def_read, and playbook.write roles request a requirement diagram. Users with sn_ac.automation_technical_user, playbook.activity_def_read, playbook.write, connection_admin, and cmdb_read roles create a requirement diagram, translate it into a Playbook Experience process, and eventually creates the automation.

Figure 1. Requirement Intake Diagram flow

1. The requester or business user submits an automation request from the Service Portal.
2. After saving the request, the fulfiller or technical user gets a review request for the automation request.
3. The fulfiller or technical user checks if the requirement diagram is available.

   If the diagram is not available, the fulfiller or technical user sends a request to the requester or business user to create a requirement diagram.

4. If the diagram is available, the fulfiller or technical user starts creating the automation in the Workflow Studio using Playbook Experience.