Yes, you can.
First, you may want to take a look at the following…
Based on that Tutorial, in your Ticket Template, you would place this Tag: {SETTING:WiFiPW}.
If that’s a little bit more complex than you need, you can still just Store the Password in SambaPOS without actually changing the Router Password. You could also hard-code the Password in one of the Templates, instead of using Program Setting {SETTING:WiFiPW}.
Printing based on a Constraint would require further Rules. You could go about it this way:
- Clone your
Ticket Template: name them appropriately, i.e. Print Bill with WiFi and Print Bill without WiFi. In 1 put in the Tag{SETTING:WiFiPW}, and in the other, remove the Tag{SETTING:WiFiPW}. - Clone your Print Bill
Print Job: name them appropriately, i.e. Print Bill with WiFi and Print Bill without WiFi. Edit the Print Jobs to use the appropriateTemplate. - Clone your Execute Print Bill
Action: name them appropriately, i.e. Execute Print Bill with WiFi and Execute Print Bill without WiFi. Adjust thePrint Jobsin the Actions to use the correctPrint Job. - Clone the
Rulewhich contains thePrint Bill Action: name them appropriately, i.e. Print Bill with WiFi and Print Bill without WiFi. Assign the properPrint Job Actionto each of theRules. - Add a
Constraintto each of theRuleswhich are opposite from one another: in 1 Rule addConstraintfor[=TN('{TICKET TOTAL}')]Greater99and in the other addConstraintfor[=TN('{TICKET TOTAL}')]Less100.
Maybe I’ll append the above setup with screenshots to the WiFi Tutorial later today…