Skip to main content
Solved

PSO/FSM Preventative Maintenance Task Time Commitments

H
Do Gooder (Partner)
Forum|alt.badge.img+7
  • HannMat
  • Do Gooder (Partner)
  • 21 replies

Good day

 

I am having an issue with my Passive Preventative Maintenance task time commitments. When tasks are created from a contract they have two time commitments: one for now, and a second for a future time commitment. The task should be scheduled for the future time commitment, not for the “Now” time commitment. When removing the “Now” commitment, it also removes the tasks from PSO (which show all tasks, but as unallocated). 

 

Is there a way to remove the time commitment that is scheduled for the “Now” time, and only keep the time commitment for future time, when generating tasks from a contract?

Best answer by Kasun Manuranga

Dear HannMat,

When a Task is created from a Contract normally it should use the Time Commitment from the Response code attached the Contract Type in your relevant Contract. This is what you see as the Future commitment.

Then if you see another commitment for Now, first it is required to identify where its coming from. Here you can check for Business Rule 40, whether its involving here i.e. verify if the rule is triggering when you create a Task from the Contract.

Normally this rule is used to enter Time Commitments in Task where No contract is involved, so we define the Input Petameters to avoid capturing the Contracts in the following way an example.

 

Also check for the RANK value, its used to setup more than one Time commitment in Tasks.

 

 

This is some general information to help your situation, you may need to validate those with your FSM configurations and disable if you see the NOW records is creating from the Business rule.

 

Thanks,

Kasun

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

3 replies

Kalana Surendra
Hero (Employee)
Forum|alt.badge.img+9

Dear @HannMat,

Usually time commits are created from Business Rules (BR). Hence the creation of the time commitment can be configured using the respective BR.  

There are several BR’s available in the baseline application and new BR’s can be created according to the requirement. 

Therefore it is possible to configure the BR to only create one time commitment, and the properties of the time commitment can be configured on the Response Code screen. 

Hope this helps.

Best Regards,

Kalana. 

Rasangi Kannangara
1 person likes this
  • Rasangi Kannangara
    Rasangi Kannangara
Kasun Manuranga
Superhero (Employee)
Forum|alt.badge.img+17
  • Kasun Manuranga
  • Superhero (Employee)
  • 148 replies
  • Answer
  • December 15, 2021

Dear HannMat,

When a Task is created from a Contract normally it should use the Time Commitment from the Response code attached the Contract Type in your relevant Contract. This is what you see as the Future commitment.

Then if you see another commitment for Now, first it is required to identify where its coming from. Here you can check for Business Rule 40, whether its involving here i.e. verify if the rule is triggering when you create a Task from the Contract.

Normally this rule is used to enter Time Commitments in Task where No contract is involved, so we define the Input Petameters to avoid capturing the Contracts in the following way an example.

 

Also check for the RANK value, its used to setup more than one Time commitment in Tasks.

 

 

This is some general information to help your situation, you may need to validate those with your FSM configurations and disable if you see the NOW records is creating from the Business rule.

 

Thanks,

Kasun

S
Sidekick (Partner)
Forum|alt.badge.img+7
  • Sowmiya
  • Sidekick (Partner)
  • 26 replies
  • April 4, 2024

Hi,
Please can you tell what is usage of rank in response code and its usage in business rule 40?
If one task has more than one time commitments how it will use rank to choose the time commitment?

 

Reply


Terms & ConditionsCookie settings

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