Skip to main content
On the backlog

IAM Schedule log - Log all Process Flows and (optionally) all Process Actions too

Related products:Intelligent Application ManagerIndicium Service Tier
  • November 20, 2021
  • 6 replies
  • 201 views
htimmermans
Robert Jan de Nie
K.Bakkenes
Arjan Sollie
Jeroen van den Belt
+50
  • htimmermans
    htimmermans
  • Robert Jan de Nie
    Robert Jan de Nie
  • K.Bakkenes
    K.Bakkenes
  • Arjan Sollie
    Arjan Sollie
  • Jeroen van den Belt
    Jeroen van den Belt
  • Harm Horstman
    Harm Horstman
  • Frank Wijnhout
    Frank Wijnhout
  • Maurice Liebregt
  • Robbert van Tongeren
    Robbert van Tongeren
  • Michael
    Michael
  • Mark Jongeling
    Mark Jongeling
  • Harold
    Harold
  • Jeroen Kole
  • Gert Groeneveld
    Gert Groeneveld
  • John Lunenburg
    John Lunenburg
  • Geurt
    Geurt
  • eurban
    eurban
  • Erwin Ekkel
  • Ruben
    Ruben
  • Freddy
    Freddy
  • Frank Junger
  • Ricky
    Ricky
  • Remco Kort
    Remco Kort
  • Arie V
    Arie V
  • Philip N
  • J. de Lange
    J. de Lange
  • mperrott
    mperrott
  • Bram G
  • Suleyman
  • Marc Ferket
  • Jochem Pieper
    Jochem Pieper
  • Peter van Leenen
  • Rick
  • Shawn Adrian Diño
  • Tejo van de Bor
    Tejo van de Bor
  • Karel
  • ruudzijl
  • Kevin Rosink
    Kevin Rosink
  • Anne Vries
  • HarryA
  • rzwambag
  • AndreKemmeren
    AndreKemmeren
  • Mark Leunissen
    Mark Leunissen
  • TurcuPaulAndrei
  • Marius Korff
    Marius Korff
  • Hans Pot
  • Robert Wijn 2
  • rbiram
    rbiram
  • BramG
  • BasWesselink
  • Raymond Gerritsen
    Raymond Gerritsen
  • pimhoek
  • Eric F
    Eric F
  • bwestra
  • Ionut
    Ionut

Arie V
Community Manager
  • Community Manager
  • 1032 replies

Currently IAM Schedule log gives us an overview of all System flows that ran, with very limited information. As an extension to this we would like to see:

  • Logging for all Process Flows - also the User-invoked ones
  • Logging for all Process Actions as a Detail table - allowing us to see start date / end date input/output variables, and status for each individual Process Action within the Process Flow. This will help us monitor, review, debug and improve Process Flows. Since for certain use cases the information contained in these variables might be sensitive, logging Process Actions should be optional.

Note: due to this functionality currently missing within the platform, we have created our own smart dynamic logic to monitor our Process Flows and Actions. This comes with some limitations however, since we have no way to establish with 100% certainty the status and end date of a Process Action. We have to resort to using the start date of the next Action as end date for the previous Action. And if the next Action is never reached we have no idea why not and therefore log an end date based on a time-out of x minutes.

Did this topic help you find an answer to your question?

6 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23
Updated idea statusNewOpen

Mark Jongeling
Administrator
Forum|alt.badge.img+23
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Jeroen van den Belt
Administrator
Forum|alt.badge.img+9
OpenOn the backlog

Jeroen van den Belt
Administrator
Forum|alt.badge.img+9
On the backlogPlanned

Arie V
Community Manager
Forum|alt.badge.img+12
  • Author
  • Community Manager
  • 1032 replies
  • January 2, 2025
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Arie V
Community Manager
Forum|alt.badge.img+12
  • Author
  • Community Manager
  • 1032 replies
  • June 17, 2025
PlannedOn the backlog

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings