Skip to main content
ashokmoorthy
Inspiring
June 4, 2024
4. Future Consideration

Provision to configure approval time limit

  • June 4, 2024
  • 4 replies
  • 43 views

Hi Team,

Today bot is fetching the approvals which are created in last 30 days. I understand the technical details (load, impact, performance,...) behind why we limited to 30 days. But unfortunately this doesn’t work for all kind of approvals.

 

We are using native Exception Approval where bot send proactive approval notification to the approvers. In this approval, depends on the impact of the exception request, it needs to be approved by one or more approvers ranging from business CIO, tower leaders, VP, CTO till CIPSO.

 

We cant expect all the different approvals happening with in the month. When approver asking for “show my approval”, bot is not fetching this approval because of the time limit aforesaid.

 

Comparatively RITM or Change approval from SNOW, the total no of request is less for Exception Approval. At least minimum we need an option to configure the approval timeout for exception approval (from 30 days to 60/90 days).   

 Enterprise Approval time limit

With this configuration, we believe bot engagement and approval via bot will be definitely more than what we have today. 

4 replies

ashokmoorthy
Inspiring
August 1, 2024

@rjoynt - Need your help here

rjoynt
Employee
August 1, 2024

I’m tracking this request @ashokmoorthy - I’ll post a few questions for you, offline.

dluckadoo
Employee
August 5, 2024

@ashokmoorthy since the 30 day lookback limit is not configurable, the easiest solution here is likely a Creator Studio use case. You can very nearly replicate the native approvals skill using an Event-triggered Path for notifications and a Query-triggered Path for approver-initiated approval lookups.

Dray
kyril.remillard
Community Manager
August 26, 2024
1. New4. Future Consideration