Solved

FSM 6.8 - Time Commit (Not Monitored)

ZRZJOLIVEIRA
Rank
Userlevel 3
Badge +7

Hi,

 

What is the logic behind Time Commit status? I was trying to understand if there is any App Parameter or Business Rule which controls it, but I’m not finding anything. 

 

I’m asking this because in our solution we have a Business Rule which creates task time commits with status ACTIVE, but FSM automatically changes it to NOT_MONITORED.

 

I check on previous FSM version (FSM 6.6) and this TC_STATUS (FSM Code) does not exist, is this new with version 6.7 or 6.8?

 

Best regards,

João Oliveira

icon

Best answer by Saranga Amaraweera 5 May 2021, 07:18

View original
João Oliveira
This topic has been closed for comments

4 replies

Nethmi Kularathne
Rank
Userlevel 5
Badge +8

Hi @ZRZJOLIVEIRA ,

 

It seems that NOT_MONITORED code value is new with FSM 6.7.

There is no such code value in FSM 6.6. But available in FSM 6.7 and higher versions

 

FSM 6.6
FSM 6.7

 

 

Best Regards

Nethmi
ZRZJOLIVEIRA
Rank
Userlevel 3
Badge +7

Hi,

 

Thank you for the confirmation, but the main question is how the Time Commit Status is controlled?

And why it’s changing to Not Monitored?

 

Best regards,

 

João Oliveira
Saranga Amaraweera
Rank
Userlevel 7
Badge +22

@ZRZJOLIVEIRA we had encountered the same issue after update 7 where it should ideally set the status to active when a new time_commit line is added. Had to add a BR to insert and update the same time_commit line to make it as active. @Nethmi Kularathne guess this needs to be directed to R&D

SAAALK
ZRZJOLIVEIRA
Rank
Userlevel 3
Badge +7

Thank you @Saranga Amaraweera for the suggested workaround!

João Oliveira
Terms & ConditionsCookie settings