We have a use case where, when a contract end date is updated, we create new reminders based upon that new contract end date.  We have no way to delete reminders associated with the old contract end date.  The Delete Reminder step doesn’t work because we don’t know the old contract end date after it has been changed.  There are a couple enhancement possibilities that could alleviate our pains in this area:

• Create a new workflow step “Get Reminders” or
• Allow us to create a JWT so that we can call the CLM APIs using the HTTP Client workflow step.  Currently, we can use the HTTP Client step with a JWT, but once the JWT expires, we have no way to retrieve a new JWT.
  • Create a new workflow step “Create JWT” or
  • Whitelist System.Security.Claims and System.Security.Cryptography C# namespaces so we can create a JWT in C#/expression builder.

The only solution I have come up with for this issue, is to have a separate service responsible for cleaning up these outdated reminders via the CLM API.  That seems like overkill and something that we should be able to automate within the platform.