Hello All - well I have finally ventured into creating some simple workflows. I need some hep defining what can be or should be done in this scenario.
Entity Data and Scenario
[=TN(’{ENTITY DATA:Customer:Points}’)]>0
I want to enable (and/or) make visible an Automation button when a Customer Entity is Selected and the Customer has enough points to convert to dollars. The above example would be modified to say 250 points (>250).
The idea is Customer asks if he has any value in his points OR User swipes customer card to bring customer up and notices he can convert Points to $$$ and asks “would you like to convert your points to dollars today Sir…”?. Typically it would be during payment but I thought I would at least get this far as Payment requires Conversion and Account Transactions then Payment to Customer Account.
Ticket Screen
Looking at the debuuger both “New” and “Active” are just a Status and not state - correct?
QUESTIONS
A. Can you create mapping just to an Entity without creating any Orders - I guess just in the “New” Status?
B. Even though we have 3 types - Entity, Order & Ticket - do the individual “Names” used in Mapping need to be Unique as how do you distinguish between a Order Status and a Ticket Status etc?
C. Do I need to create an Order State to Map this correctly as the rule debugger shows that Entity State is made to “Accrued”?
D. Can you specify [=TN(’{ENTITY DATA:Customer:Points}’)]**<=**0 (less than or equal to) in a constraint or do we need to use 2 lines or do we need to use the && clause?
E. When I used [=TN(’{ENTITY DATA:Customer:Points}’)]=0 the rule fired as well which is incorrect, what is wrong?
[EDIT]
F. How can I display a Dollar converted value in the “Convert Points” automation button caption?
For Example 350 Points = 350/250 = 1.4 Therefore we only convert whole dollars and show $1 ?
Generally folks once I get this away I should be ok to create complete workflows so looking forward to the answers, thanks.
Mapping a button? not following that one, automation commands would be relative to their position, ie order line would look to order state, ticket to ticket state.
If its right see above,[quote=“pauln, post:1, topic:8590”]
C. Do I need to create an Order State to Map this correctly as the rule debugger shows that Entity State is made to “Accrued”?
[/quote]
Again I think you would need to update ticket state for ticket visible command.
I asked in the past if you could map button to state isnot != but you cant, if that doesnt work its likely similar, mapping is positive/=
try [=TN(‘{ENTITY DATA:Customer:Points}’)] == 0 or loose the TN … ‘{ENTITY DATA:Customer:Points}’ == ‘0’
Oh crap really , so if I have used “Display Under Ticket” then I must effect a Ticket State?
Don’t suppose there a place for Entity - I assume you are going to say an Entity Screen?
Interesting, what States do you effect if you have the button listed under “Payment Screen”?
Since it is available grouped with ticket I would guess it is bound to ticket states.
Im pretty sure you can, would be surprised if not, the topics about menu buttons showing OUR OF STOCK based on dynamic product button headers - guessing same should be possible for automation commands if not it would be a good request.
Remember somewhere the <panel> tag could be used for dynamic button colour etc so expect {REPORT or {CALL:xx} will probably work…
Remember it won’t create a real ticket until orders are added and submitted. So you could manipulate entities and states and close ticket and no ticket will be made.
Convert Points\r[=F(TN('{ENTITY DATA:Customer:Points}')/2,'#')] this gives me 5/2 displays 3. I just want it to display 2 as I not going to transfer part points…
Its only for display purposes, I will use proper calcs during the Account Transaction Document.
