Message pop up problem

Craig_Farman · January 9, 2019, 2:53pm

Hi Guys

My setup briefly is this.

3 types of Membership Cards linked to 3 different types of entity

I use a Numberpad Entered Rule to determine the correct entity from a swipe card and update the entity state to selected.

I then use a Entity State Rule to fire a message on screen which i want to display things like the name of the member and the number of points they have etc.

When I reference the Data in the message prompt using the {ENTITY DATA:} commands they are not populating with information from the entity?

Any ideas

Cheers

Craig_Farman · January 9, 2019, 2:55pm

Craig_Farman · January 9, 2019, 2:56pm

Jesse · January 9, 2019, 2:57pm

It can’t show anything unless entity is loaded or in a ticket. When are you changing state?

Craig_Farman · January 9, 2019, 2:59pm

Has it not already loaded as you can see it shows the Employee Entity and the Test Staff Pass has been accessed.

Thanks

Jesse · January 9, 2019, 3:00pm

Try ENTITY DATA:Employee:Name

Craig_Farman · January 9, 2019, 3:01pm

No Difference I get the same solution it does it with all 3 Entities.

Sorry

Jesse · January 9, 2019, 3:02pm

Try ENTITY NAME:Employee

Jesse · January 9, 2019, 3:03pm

Show us your custom fields.

Craig_Farman · January 9, 2019, 3:04pm

Craig_Farman · January 9, 2019, 3:04pm

Jesse · January 9, 2019, 3:05pm

So did you try ENTITY NAME:Employee?

Craig_Farman · January 9, 2019, 3:05pm

Yeah still doesnt read the information from the selected Entity

Jesse · January 9, 2019, 3:05pm

Add an item to ticket then try. Maybe it’s wrong event.

Craig_Farman · January 9, 2019, 3:08pm

Still Nothing im afraid I appreciate your help in this matter.

Jesse · January 9, 2019, 3:09pm

How are you changing state?

Craig_Farman · January 9, 2019, 3:10pm

Craig_Farman · January 9, 2019, 6:57pm

Is it possible to put a constraint into the message action box to only execute if it matches a certain Entity Type?

JTRTech · January 9, 2019, 7:10pm

Yes. The constraint field of each action can be set.
It would use == or != For typical equals or not equals.
General for string expressions like entity name or type you would quote both sides of the == like ‘{EXPRESION A}’ == ‘XYZ’
Check printer and report expressions for potential expession. Note not all are available on every rule type. Ticket level generally are, order level print template expressions would need to be on order related event unless it’s a more general report type expression.

Craig_Farman · January 9, 2019, 7:17pm

Thanks Guys ive sorted the problem by executing an automation command to trigger the pop up dependant on the entity type so far seem to be good.

Thanks