Senpiper
  • Introduction to Senpiper One Resource
  • Getting started
    • Overview
    • Log in to the platform
    • Web workspace
    • Mobile Applications
    • White-labeled Apps and custom domains
  • Groups/Applications
    • Groups Overview
    • How to create groups?
    • Open vs Closed groups
    • Managing group members
      • Types of group members
      • Manual Group member management
        • Adding users individually
        • Adding users in bulk
        • Removing users
      • Automated user management
        • How to define criteria for adding users?
        • How to auto-remove users?
        • User Removal Alerts and Task Delegation
    • Group Details on web
      • Form Table View
      • Kanban View
      • Group chats
      • Pending task (assigned to you)
        • How to access the tasks assigned to you?
        • How to take actions on the tasks assigned to you?
        • How to toggle between different views?
    • Group Details on Mobile Apps
      • Managing Group Views
      • Group Chat Features
      • Form Submissions
        • Form card settings
      • Media Directory
        • How to create Media folder ?
        • How to upload media ?
        • How to delete Media ?
      • Pending Tasks
      • Group Settings
  • Media folders
    • Overview
    • How to access the Media Folders?
    • How to create media folders?
    • How to upload media files in folders?
    • How to delete media folders and files?
  • Scheduler
    • Overview
  • HOW TO CREATE APPLICATIONS
    • Overview
    • Tools to create an application
  • USER MANAGEMENT
    • Introduction
    • Managing users
      • User lists
        • How to create user lists?
        • How to create users?
        • How to add custom user list parameters?
      • How to add users to a user list?
        • Adding multiple users to a user list
      • More actions
        • Viewing users
        • Searching users
        • Downloading user lists
        • Delegating tasks
        • Viewing the change log of a user profile
        • Editing users
        • Deleting users
        • Blocking users
        • Unblocking users
        • Unlocking user
        • Granting permissions to users
    • Managing custom roles
      • Creating roles
      • Assigning custom roles to users
      • Removing custom roles from users
      • Granting permissions to roles
    • Roles and Users for the Reimbursement Use Case
  • FORM BUILDER
    • Introduction
    • How to create forms?
      • Basic details
      • Adding fields and saving a form
        • Types of fields
        • Default field settings
        • Individual field settings
        • Creating master records
        • Language settings for fields
      • Additional form settings
        • Conditions
          • Manage field settings
          • Copy field values
          • Conditional values of fields
            • Master Mapping
          • Validate field values
          • Calculate field values
          • Validate location
          • Face Matching
          • Append values to a field
        • Submit button settings
        • Configure pre loader
        • Configure post loader
        • Set form card layout
        • Set form table properties
    • Advanced concepts
      • Parent-child form settings
      • Using report data in forms
    • Editing forms
    • Deleting forms
    • More form options
  • WORKFLOW BUILDER
    • Introduction
      • Overview
      • Navigating workflow builder
      • How to add a new workflow?
      • How to view draft workflows?
    • Defining workflows
      • Define conditions for a workflow step
      • Define Workflow Actions
        • Configuring communication settings
        • Configuring a conditional assignee
        • Selecting an assignment strategy
      • Define workflow Step
        • Updating the status for a step of the workflow
        • Configuring button settings for a step of the workflow
          • Basic details
          • Form edit settings
          • Assignment settings
          • Comment log settings
          • Auto trigger settings
          • Time settings
      • Ending workflow
    • Editing workflows
    • Deleting workflows
    • Designing the reimbursement workflow (Path 1)
    • Designing the reimbursement workflow (Path 2)
  • ALARM BUILDER
    • Introduction
    • Alerts for form submission
      • Add New Alarm
        • Configuring the basic details
        • Defining the communication type
          • Send an Email
          • Send an SMS
          • Send an App Notification
        • Setting up the schedule for alerts
      • Viewing alarm event details
      • Editing an existing alarm
      • Deleting an existing alarm
    • Alarms for Custom Data Exports
      • Add a new alarm
        • Configuring Basic Details
        • Configure Content
        • Define Schedule
      • View Alarm event details
      • Clone a Alarm
  • General System Settings
    • Introduction
    • Authentication settings
      • Login option Preferences
      • Password settings
      • Custom URLs
    • Organization Branding
    • Custom Settings
    • Enable Sign-Up
      • Build a Sign-up form
      • Settings for Sign-up form
      • Customize Sign-up form
  • DIGITIZE A SAMPLE PROCESS
    • Overview of the process
    • Step 1: Register a company
    • Step 2: Create a group/Application
    • Step 3 : Design forms
    • Step 3: Create Process flow
    • Step 4 : Set up the communication
    • Testing the platform
  • Process migration
    • Introduction
  • Different types
  • Steps for migrating any process
Powered by GitBook
On this page
  • Step 2:
  • Step 3:
  • Step 4:
  • Step 5:
  • Step 6:
  • Step 7:

Was this helpful?

  1. WORKFLOW BUILDER

Designing the reimbursement workflow (Path 2)

PreviousDesigning the reimbursement workflow (Path 1)NextIntroduction

Last updated 2 years ago

Was this helpful?

Now let’s look at path 2. This path is a complex one and involves 8 more steps of approval as shown in the workflow diagram.

Step 2:

Like in path 1, the level 1 approver of this step is the manager.

The manager can perform 3 actions. He can either approve, reject or ask for clarification from the initiator. The buttons Approve, Reject and Provide clarification can be created in a similar manner as they were created in path 1. If the manager clicks on Provide clarification, the Update button should be enabled for the initiator by which they can make the required changes to the form. This is where the Assignment Settings come into the picture for the Update button.

As you can see, we have selected step n – 2 which means that the Update button is enabled at step n – 2 which is the step of the initiator. The workflow ends if the Manager clicks the Reject button. If the Manager clicks the Approve button, the flow is transferred to the Department Head which brings us to step 3.

Can you create the three buttons now that you have all the information?

Step 3:

As in step 2, the Department Head can either approve or reject the request. Here, we need to create two buttons Approve and Reject in a similar manner as we created in step 2. If the Department Head clicks Reject, then the flow ends here. If the Department Head clicks the Approve button, the flow is transferred to the Finance Team which brings us to step 4. The Finance Team consists of 5 team members. This is where Assignment Strategy will come into the picture. We have selected the Assignment Strategy as Round Robin which means that this step will be assigned to the members of the Finance Team one by one. Only one member will be assigned to a step at a time. For another instance of the workflow, this step will be assigned to the next member in the sequence.

Can you create the two buttons and configure an assignment strategy for the Approve button?

Step 4:

In this step, the flow is assigned to a member of the Finance Team. The Finance Team can either approve, reject or ask for clarification from the initiator. The buttons Approve, Reject and Provide clarification can be created in a similar manner as they were created in step 2. If the manager clicks on Provide clarification, the Update button should be enabled for the initiator by which they can make the required changes to the form. If the Finance Team member clicks on Approve, then the flow is transferred to the Finance Head.

Can you follow step 2 for path 2 and create the 3 buttons in a similar manner?

Step 5:

In this step, the flow is assigned to the Finance Head. The Finance Team can either approve, reject or ask for clarification from the member of the Finance Team. The buttons Approve, Reject and Provide clarification can be created in a similar manner as they were created in step 2. When the Finance Head clicks on Provide Clarification, the Update button should be enabled for the same Finance Team member who approved the request. Also, if the Finance Head clicks on Approve, the Finance Head should be able to select the assignee for the next step. The workflow ends if the Finance Head clicks on Reject. Let’s take a look at the settings configured for achieving this.

As you can see in the Assignment Settings for the Approve button, we have selected Audit Team as the user list from which the Finance Head can select the next assignee. Also, as you can see in Basic Details, the Update button will be enabled for the Finance Team member when the user clicks on Provide Clarification.

Step 6:

In this step, the flow is assigned to the Audit Team member selected by the Finance Head in the previous step. The Audit Team member processes the payment and assigns the flow to the Admin team for the next step based on the phone number provided in the form. This is where the Conditional Assignee settings come into the picture.

As you can see in the Conditional Assignee Settings for the Audit Team, the next assignee is selected based on the Phone Number field in the form. The system matches the value of this field with the phone numbers of the users in the EMPLOYEE user list.

​​Now that we have learned to configure a conditional assignee based on the phone number, can you configure one based on the email address field in the form?

Step 7:

This is the last step of the workflow. The assignee selected at the previous step will now complete the payment and the workflow ends here.

The initiator is to be notified once the payment is processed. Let's look at the Communication Settings needed to achieve this.

As you can see, we have configured an email notification to be sent to the initiator as soon as the admin team processes the payment.

Path 2 of the workflow ends here.

Now that we have learned to design workflows using our platform, can you design one for your application?

Assignmenet Settings
Assignmenet Strategy
Add Button Details
Conditional Assignmenet
Configure an Email