Edit

Release Management Guide

Business Process description

• Process name
• Processing hours
• Process description by steps
• Input and 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

• All bots and Manual Tasks should be developed and tested in local PC (or development VDI), i.e. Local Control Tower.
• Developers should use WorkFusion Studio to record or manually code bots.
• Developers should use suggested by WorkFusion RPA Framework to build RPA Java projects architecture across organization.
• All code should be stored in GIT for versioning and as a repository. Only after that can they be imported to Central Control Tower.
• GIT artifacts are: bot configurations and BP package(for rules and connections persisting).
• Each artifact (BP and configurations) should be versioned.
• No bot or Manual Task development should be done in Control Tower.
• Business Process creation should NOT be done in Control Tower, using imported bots or Manual Tasks.
• All changes are made in NOT automated BP version.
• Changes in automation subprocess should be done in a separate copy of the automation.

Production Deployment

Step 1: Email

Send an email with release notes and filenames to the manager.

Email template sample is as follows:

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: Business Process 1 link Business Process 2 link Additional files link 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

Log in 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 Business Processes > View all Business Processes.
2. Click the latest Business Process you want to migrate and open it.
3. Click the Business Process Packages tab and click Download.
4. A zip file will be downloaded in the default folder on the local machine.
5. Repeat steps 1-3 for all new Business Processes that should be deployed.
6. Perform some additional steps from the email.

Step 4: Upload Business Process via UI

The detailed process is described here

1. Click Business Processes > View all Business Processes.
2. Click Create Business Process and Import package in the top right corner.
3. Upload the Business Process package file.
4. Click 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 described in the email.

Step 5: Verify deployment

1. Click Business Processes > View All Business Processes.
2. Make sure that you can see and open BPs you 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 the Dev or UAT instance and move the trained model to Prod. On the Prod instance, model retraining should be disabled.

Copy model from Dev and UAT environments to PROD

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

Apply model to Manual Task

1. Open the Business Process with a Manual Task.
2. Open Automation parameters for the task.
3. Click the arrow icon (▼) to the right from the Edit button and click Configure.
4. Start typing the Experiment Group name (the folder name on S3 from the -resources folder). The autocomplete displays all the available variants. Mind that the autocomplete loads only experiment data for the selected model type.
5. Experiment Id is automatically loaded if Experiment Group is selected from the autocomplete list.
6. Save the Task.

Turn off model retraining

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

Infrastructure

• Security
• Hardware requirements
• Analytics
• High Availability and Multi-tenancy

Troubleshooting

Normal events

Business exceptions are as follows:

Event Description	BOT Actions	Prod Support Actions	Operations Actions

Exception events

Unhandled exceptional cases are as follows:

Event Description	BOT Actions	Prod Support Actions	Operations Actions

Generic events

Scheduled server and BOT restarts are as follows:

Event Description	BOT Actions	Prod Support Actions	Operations Actions

Business Process guides

Work with Business Process

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) and 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 WorkFusion Windows Server (Nodes).

BOT run schedule and load distribution

Process Name	Number of BOTs	Start - End Time	Frequency

Production support coverage

Process Name	Start Time	End Time	Owner

Business system monitoring

Put the description here if required.