Skip to main content
Solved

PSO: Additional Attribute from Cloud is updated only via LOAD


Forum|alt.badge.img+7

Hello, 

 

I have created an additional attribute based on a custom field. In this case, the number shown in PSO can change pretty often. Available capacity can be 10, than change to 9 and so on.

Shouldn’t this change go directly to PSO? This is my understanding from the mapping file. However, in our test environment, the data gets updated only with LOAD.

IFS Cloud: 24R2

 

Does anyone have any idea here?

Thank you,

Iulia

Best answer by Alexander Heinze

That was exactly my expectation. When something changes on the task, this may affect the custom field, so that the new value gets sent to PSO. If the CF doesn’t change, there is no harm, it’s just a slightly bigger change message.

Sounds like the only thing you are missing is that the change message is also triggered when the CF changes (the reason is likely that your CF is stored in a CF table, not the main table)? In that case you could

  • customize the logic
  • raise an idea for R&D
  • as a workaround let an update of your CF trigger the update of one of the “monitored” fields (hoping this doesn’t happen every second...)
View original
Did this topic help you find an answer to your question?

4 replies

Alexander Heinze
Superhero (Employee)
Forum|alt.badge.img+23

You have created an Activity Additional Attribute based on a custom field on task, correct? When do you expect the data to get updated? On an existing task when a change happens? Or on a newly created task?

My expectation/guess would be that the attribute itself becomes available in PSO upon LOAD (never tried if a CHANGE is sufficient), and when a new task is created it should send the task’s capacity. When you update a task (e.g., the duration), I’m not sure if the new value of the CF is sent as well.


Forum|alt.badge.img+7
  • Author
  • Sidekick (Partner)
  • 53 replies
  • March 28, 2025

Hi ​@Alexander Heinze, yes, the attribute is based on a custom field on task. The expectation was that the data gets updated also when the value of the custom field changes on the existing task.

Thank you for the hint. As you mentioned, I have tried to change for example the duration of the task. In that moment, also the data of the attribute got updated. So this gets update not only with load, but also when a standard change on the task happens. Is this a normal behaviour?

 

Best regards,

Iulia


Alexander Heinze
Superhero (Employee)
Forum|alt.badge.img+23

That was exactly my expectation. When something changes on the task, this may affect the custom field, so that the new value gets sent to PSO. If the CF doesn’t change, there is no harm, it’s just a slightly bigger change message.

Sounds like the only thing you are missing is that the change message is also triggered when the CF changes (the reason is likely that your CF is stored in a CF table, not the main table)? In that case you could

  • customize the logic
  • raise an idea for R&D
  • as a workaround let an update of your CF trigger the update of one of the “monitored” fields (hoping this doesn’t happen every second...)

Forum|alt.badge.img+7
  • Author
  • Sidekick (Partner)
  • 53 replies
  • March 28, 2025

Hello ​@Alexander Heinze, as always, thank you for the help and all ideas. This is very helpful:)


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