Delayed deployment of a Release / Process / Object

[Paweł_Imiołek]

Hello,

On our project we maintain some Processes that work 'sequentially' for entire month, and when a new month begins, they start a new cycle. Now let's imagine we want to deploy a new release, taking effect in the next month not to corrupt current outcomes. Then we have to remember to do it. If there are more deployments to recall, it starts to be complex. I suggest to consider some delayed deployment, so an admin can import a release / Process / Object, selecting the time when it takes effect. Then nothing to remember, just it will take effect itself.

Regards,
Pawel

[simone.tomaCNH]

Hi Pawel,

That's a great idea.

In our case, in order to avoid having to manage each release manually and to lighten the workload of the AMS team, I developed a bot triggered by a specific email with the release attached.

The bot checks the release content (standard objects not to be replaced, credentials, environment variables, etc.) and automatically uploads the release using automateC.

In order to track the activity, I developed an integration with ServiceNow to open a ticket, assign it, and close it so that all managed releases can be tracked on a dashboard. In your case, you could send a scheduled email with the release. This way, it will be imported and ready only after a certain date.

Simone

[Paweł_Imiołek]

Hi Simone,

Your concept is great, too.
Do you use a separate license for it or your flow is triggered without such a need?

Thanks!
Pawel

[simone.tomaCNH]

Hi Pawel,

This is a standard process that is triggered by an email, so it does not have a dedicated license.

In our case, we have a custom orchestrator, developed by third parties, that launches the process.

Another idea is to use an external system (e.g., Outlook Rules or an SMTP server) that intercepts the email and launches the process via Blue Prism's REST API.

In fact, you can expose the process as a Web Service and launch your bot directly.

Simone