10.1.4.1

Edit

Release management

Business Process description

  • Process name
  • Processing hours
  • Process description by steps
  • Input / Output of the process
  • Exception queue and human in the loop
  • Describe all possible flows of the process
    • Positive
    • Negative
    • When human should be in there

Development flow

  1. All bots and manual tasks should be developed and tested in local PC (or development VDI), i.e. Local Control Tower.

  2. Developers should use WorkFusion Studio to record or manually code bots.

  3. Developers should use suggested by WorkFusion RPA Framework to build RPA Java projects architecture across organization.

  4. All code should be stored in GIT for versioning and as a repository. Only after that can they be imported to Central Control Tower.

  5. GIT artifacts are: bot configurations and BP package(for rules and connections persisting).

  6. Each artifact(BP and configurations) should be versioned.

  7. No bot or manual task development should be done in Central Control Tower.

  8. Business process creation should NOT be done in Central Control Tower, using imported bots/manual tasks.

  9. All changes are made in NOT automated BP version.

  10. Changes in automation subprocess should be done in separate copy of Automation Use Case.

Production deployment

Step 1: Email

Send an email with release notes and with file names to the manager

Email template sample

Subject WorkFusion Artifacts Deployment ${ArtifactVersion}
Body

The following artifacts are ready to be deployed to production:

  • Business process 1
  • Business process 2

Business process package and all necessary files to deploy:

Release notes:

  • Fixes
  • Improvements
  • New features

Specific instructions to deploy package to prod. Something else that is more than import package. All this information will be used in Steps 4, 5, 6.

Step 2 – Access WorkFusion server

Login to WorkFusion prod Web UI:

  • URL: WorkFusion login page
  • Credentials: WorkFusion login credentials
  • The landing page will be the WorkFusion dashboard (see sample image below)

Step 3 – Download business packages from DEV server

  1. Click on Business Processes -> View all business processes
  2. Click on the latest Business Process you want to migrate and open it
  3. Click on “Business Process Packages” tab and click on “Download”
  4. Zip file will be downloaded in default folder on local machine.
  5. Repeat the step 1- 3 for all new Business Processes that should be deployed
  6. Some additional steps from the email that are required

Step 4 – Upload business process via WorkFusion UI

Detailed process is described here

  1. Click on Business Processes -> View all business processes
  2. Click Create business process & “import package” in the top right
  3. Upload the business process package file
  4. Click on View Business process (Task) to verify the imported business process
  5. Repeat steps 1-4 for all new Business Processes that should be deployed
  6. Perform additional actions that described in email

Step 5 – Verify deployment

  1. Click on business processes & click “View All Business Processes”
  2. Make sure that you can see and open BP's that you've imported in Step 5

Step 6 – Additional verification from Email

Follow the additional verification steps from the email

Move ML model to the environment

The recommendation is to train model on Dev / UAT instance and move the trained model to Prod. On Prod instance model retrain should be disabled.

Copy the model from Dev/UAT environments to Production one

  1. Copy hypermodel from UAT instance to PROD instance s3://vds-models/{hypermodelName}
  2. Copy trained model from UAT instance to PROD instance s3://vds-resources/{trainedModelName}
  3. Copy s3://vds-models/models.prod from Dev/UAT instance to PROD instance
  4. Restart vds services on PROD linux server: service vds restart

Applying the model to Human Task (HT)

  1. Open the Business Process (BP) with a human task (HT)
  2. Open Automation parameters for the task (Automation Use Case and ML Model)
  3. Click the arrow icon (▼) to the right from the Edit button and click Configure
  4. Start typing Experiment Group name (folder name on S3 from *-resources folder) – autocomplete displays all the available variants
    1. Note: Auto complete loads only experiment data for the selected model type
  5. Experiment Id is automatically loaded if Experiment Group was selected from auto complete list
  6. Save the Task

Turning off automated retrain of the model

  1. Select the required automation Business Process (BP) from the list. It should be marked with “Automation available” label
  2. Open it and go to “Design” tab. Find all Automation Sub Business Processes – they are highlighted with green color
  3. Expand the Sub Business Processes by clicking on the cross at the left top corner of the box
  4. Open the first step of the Sub Business Process by double-clicking on the first box inside of expanded area (usually it ends with Settings word)
  5. Scroll down and make sure that “User Defined” option is selected for “Retrain the model as more data collected” field and the value in “Retrain records count” input field below is set to 0

Infrastructure

Troubleshooting

  • normal events

Business exceptions

Event DescriptionBOT ActionsProd Support ActionsOperations Actions








  • exception events or unhandled exceptional cases
Event DescriptionBOT ActionsProd Support ActionsOperations Actions








  • generic events

Scheduled Server / BOT restarts

Event DescriptionBOT ActionsProd Support ActionsOperations Actions








Bot onboarding process

  1. Review the server capacity and confirm if the hardware is sufficient to host the required number of BOTs. In case the server capacity is not sufficient, then the Production Support team works with Customer Infra to increase the server capacity
  2. Production Support team performs any changes to WorkFusion components (such as configuration of additional nodes) / server configuration
  3. Customer Infra creates network credentials (BOT IDs) with access to WorkFusion Windows Server
  4. Customer Infra adds the BOT IDs to the group that will provide the access to RDP into the Windows Server
  5. Customer Infra adds the BOT IDs to the group that will provide the access to the systems to work with
  6. Production Support team configures user account profiles on the Work Fusion Windows Server (Nodes)

Bot run schedule and load distribution

Process NameNumber of BOTsStart - End TimeFrequency








Production support coverage

Process NameStart TimeEnd TimeOwner








← ImplementationProduction support →