Release management

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 on local computers (or in the development VDI)—that means, in local Control Tower.
• Developers should use Work.AI Developer to record or manually code bots.
• Developers should use the RPA framework suggested by WorkFusion to build the RPA Java project architecture in your organization.
• All code should be stored in GIT. Only after that, it can be imported to the central Control Tower.
• GIT artifacts include Bot Configurations and BP packages (for persisting rules and connections).
• Each artifact (BP and Bot Configurations) should be versioned.
• No bot or Manual Task should be developed in the central Control Tower.
• Business Process should not be created in the central Control Tower, using imported bots or Manual Tasks.
• All changes are made in the BP version that is not automated.
• The automation subprocess should be updated in a separate copy.

Production deployment

Step 1: email

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

The email template sample is as follows:

Section	Content
Subject	WorkFusion artifact deployment ${ArtifactVersion}
Body	The following artifacts are ready to be deployed to production: Business Process 1 Business Process 2 The Business Process package and all necessary files to deploy: Business Process 1 link Business Process 2 link Additional file links Release notes: Fixes Improvements New features Specific instructions to deploy a package to production Something else concerning the import package All this information will be used in steps 4, 5, 6.

Step 2: access WorkFusion server

Log in to the WorkFusion production web interface:

• URL: WorkFusion login page
• Credentials: WorkFusion login credentials

The landing page is the Analytics page.

Step 3: download business packages from DEV server

1. Click Business Processes > View all.
2. Click the latest Business Process you want to migrate and open it.
3. In the Business Process, navigate to the Packages tab and click Download.
4. The zip file is 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 the additional steps as required in the email.

Step 4: upload Business Process

1. Click Business Processes > View all.
2. In the top right corner, click the ellipses button and select Import package.
3. Upload the Business Process package file.
4. Click Preview Package to verify the imported Business Process.
5. Repeat steps 1-4 for all new Business Processes that should be deployed.
6. Perform the additional steps as required in the email.

Step 5: verify deployment

1. Click Business Processes > View All.
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 the environment

The recommendation is to train a model on the Dev or UAT instance and move the trained model to production.

Copy model from Dev or UAT to production

1. Copy the pipeline from the UAT instance to the PROD one s3://vds-models/{pipelineName}.
2. Copy the trained model from the UAT instance to the PROD one s3://vds-resources/{trainedModelName}.
3. Copy s3://vds-models/models.prod from the Dev or UAT instance to the PROD one.
4. Restart VDS services on the PROD Linux server: service vds restart

Infrastructure

• Security
• Hardware requirements

Troubleshooting

Normal events

Business exceptions

Event description	Bot actions	Production support actions	Operation actions

Exception events

Unhandled exceptional cases

Event description	Bot actions	Production support actions	Operation actions

Generic events

Scheduled server or bot restarts

Event Description	Bot actions	Production support actions	Operation 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 the Customer Infra to increase the server capacity.
2. The Production Support team applies changes to the WorkFusion components (such as configuration of additional nodes) and server configurations.
3. The Customer Infra creates network credentials (Bot IDs) with access to the WorkFusion Windows Server.
4. The Customer Infra adds the Bot IDs to the group that provides RDP access to the Windows Server.
5. The Customer Infra adds the Bot IDs to the group that provides 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 and end time	Frequency

Production support coverage

Process name	Start time	End time	Owner