Manage Requirements

Overview

The Requirements tab helps you define and organize the core activities, steps, and actions that shape your application. By breaking down functionality into manageable components, you can ensure your application aligns with user needs and business goals. Use the Requirements tab to visually map and refine your application's key processes.

In the Requirements tab, you can

• add an activity,
• add a step,
• add an action,
• connect design objects to actions, and
• fine-tune your requirements

Add an activity

To manually add a new activity:

1. On the Requirements tab, click ADD ACTIVITY.
   Result: The Add Activity card displays.
2. Enter a clear and concise title for your activity in the Name field.
   Tip: The name should be specific enough to convey the activity's purpose at a glance. Avoid overly general names and ensure it reflects the main function of the activity within your application. For example, instead of "Process," use something like "Customer Onboarding" or "Claim Submission."
   
   
3. (Optional) Enter a description of the activity's purpose or objective in the Goal field.
4. Click the checkmark to save.

Add a step

To manually add a step to an activity:

1. On the activity card, click the ADD dropdown menu.
2. Select Step.
   Result: The Add Step card displays.
3. Enter a clear and concise title for the step in the Name field.
   Tip: The name should be specific enough to convey the step's purpose at a glance. Avoid overly general names and make sure it reflects the key function of the step. For example, instead of "Process Step," use something like "Verify Customer Details" or "Approve Payment."
   
   
4. Click the checkmark to save.

Add an action

To manually add an action:

1. You can add an action in two ways:
   • From the Activity card: Click the ADD dropdown and select Action.
   • From the Step card: Click the ADD ACTION button on the Step card.
     Result: The Add Action card displays.
2. Enter a clear and concise title for the action in the Name field.
3. (Optional) Select the action type in the Type dropdown list.
4. (Optional) Select the persona responsible for the action.
5. Click the checkmark to save.

Connect design objects to actions

You can associate design objects, such as record types, process models, reports, and interfaces with any action. This ensures that all relevant objects are linked to the correct actions, making it easier for developers to understand how the application is structured. It also simplifies ongoing maintenance by clearly mapping the relationships between design objects and actions for future reference.

To connect a design object to an action:

1. Click the action you want to modify.
   Result: The All Objects screen displays.
2. Select and complete one of the following options.
   • NEW: This option allows you to add a new object to your application. After creating the object, you can return to the Plan view, where the object will automatically be connected to your action.
   • ADD EXISTING OBJECTS: This option lets you connect an existing object from your application to the action. You can add multiple objects at the same time.

Once you're done, the design objects will appear in the object list under the action. You can view details such as their name, description, and last modified date. Use this view to manage the objects associated with the action.

Fine-tune your requirements with drag and drop

A well-organized layout makes it easier for your team to understand the overall structure and flow of the application. Here are some tips for customizing your requirements for clarity:

• Arrange related steps and actions together: Arrange related activities together in a way that reflects your application's workflow. This makes it easier to navigate through the plan and ensures that the flow of processes is intuitive.
• Use clear and descriptive names: Ensure that each activity, step, and action has a clear, descriptive name that reflects its function. Avoid generic names—specific labels help users understand the purpose of each element at a glance.
• Rearrange for better flow: You can drag and drop activities, steps, and actions to reorder them in a way that reflects the natural progression of your application's workflow. Arrange steps in the order that users or Appian will follow for better clarity.
• Break down complex processes: If an activity becomes too complex, break it down into smaller, more manageable activities or steps. This avoids overwhelming the plan and makes each part of the process clearer.

Feedback