Release management

Business Process description

• Process name
• Processing hours
• Process description by steps
• Input or 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 project architecture across the 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 or manual tasks.
9. All changes are made in NOT automated BP version.
10. Changes in the automation subprocess should be done in a separate copy of the Automation Use Case.

Production deployment

Step 1: email

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

The 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 a 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 the WorkFusion prod Web UI:

• URL: WorkFusion login page
• Credentials: WorkFusion login credentials
• The landing page will be the WorkFusion dashboard (see a 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 the Business Process Packages tab > Download.
4. The .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 additional steps from the email that are required.

Step 4: upload Business Process via WorkFusion UI

tip

The detailed process is described here.

1. Click on Business Processes > View all business processes.
2. Click Create business process & import package at the top right corner.
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 steps described in the email.

Step 5: verify deployment

1. Click on Business processes > View All Business Processes.
2. Make sure you can see and open the business processes you've imported in step 5.

Step 6: additional verification from email

Follow the additional verification steps from the email.

Move ML model to environment

The recommendation is to train a model on Dev or UAT instance and move the trained model to prod. On the prod instance, model retrain should be disabled.

Copy model from dev or UAT environments to production one

1. Copy the hypermodel from the UAT instance to the PROD instance s3://vds-models/{hypermodelName}.
2. Copy the 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

Applying 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 the Experiment Group name (the folder name on S3 from the *-resources folder). The autocomplete displays all the available variants.

note

The autocomplete loads only experiment data for the selected model type.

Experiment Id is automatically loaded if Experiment Group was selected from the autocomplete list.

5. Save the Task.

Turning off automated model retrain

1. Select the required automation Business Process (BP) from the list. It should be marked with the Automation available label.
2. Open it and go to the Design tab. Find all automation business subprocesses: they are highlighted with the green color.
3. Expand the business subprocesses by clicking on the cross at the left top corner of the box.
4. Open the first step of the business subprocess by double-clicking on 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

Troubleshooting

Normal events

Business exceptions

Event Description	BOT Actions	Prod Support Actions	Operations Actions

Exception events

Unhandled exceptional cases

Event Description	BOT Actions	Prod Support Actions	Operations Actions

Generic events

Scheduled Server or BOT restarts

Event Description	BOT Actions	Prod Support Actions	Operations 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, the Production Support team works with Customer Infra to increase the server capacity.
2. The 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 the WorkFusion Windows Server.
4. Customer Infra adds the BOT IDs to the group that will provide access to RDP into the Windows Server.
5. Customer Infra adds the BOT IDs to the group that will provide access to the systems to work with.
6. The 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