Solved

Adjust badge based on detail reference.

  • 22 December 2023
  • 4 replies
  • 97 views
B
Rank
Userlevel 1
Badge +4

Hello,

we currently use a badge to show how many interface messages are in status ‘queue’. This works great when you display interface messages as a main subject, but when referenced from the perspective of a interface message type, the badge shown in the detail tab still counts all interface messages in status 'queue',  despite the interface message type to which they are linked. Is there currently something on the backlog to readjust these badges automatically based on the reference from which they are shown, or is this something a developer needs to take into account while developing? If the latter, what exactly is a best practice in this?

 

Thanks in advance!

icon

Best answer by Arie V 2 January 2024, 19:28

View original
This topic has been closed for comments

4 replies

E
Rank
Userlevel 6
Badge +16

This is not on the backlog and this behavior is by design. So indeed you need to take this into account when creating an application. Feel free to create an idea for this in the ideas section. 

Freddy
Userlevel 5
Badge +16

Hello,

we currently use a badge to show how many interface messages are in status ‘queue’. This works great when you display interface messages as a main subject, but when referenced from the perspective of a interface message type, the badge shown in the detail tab still counts all interface messages in status 'queue',  despite the interface message type to which they are linked. Is there currently something on the backlog to readjust these badges automatically based on the reference from which they are shown, or is this something a developer needs to take into account while developing? If the latter, what exactly is a best practice in this?

 

Thanks in advance!

To create what you want you need to create variants per message type and use the variant_id in the logic of the badge. In the model you choose at detail-level which variant it should use. 

This is not a dynamic concept indeed, so you have to pre-create details for each message type and hide/show them using a context procedure. 

 

LEF - The future favors the brave. [lef.tec.br]
A
Rank
Userlevel 6
Badge +10

@BramG If I understand your question correctly, you would like to see (for example):

  • MAIN: total in status ‘queue’
  • DETAIL: total in status ‘queue’ for the selected MAIN Message Type

If understood correctly: that should work using the col_id parameter for filtering on the Foreign Key id(s) as explained in the Docs: https://docs.thinkwisesoftware.com/docs/sf/business_logic#badge

B
Rank
Userlevel 1
Badge +4

Eventually solved by extending my where clause by evaluating if the @interface_message_type = interface_message_type (for details) or @interface_message_type is null (for main). Thanks for the replies!

Terms & ConditionsCookie settings