Thanks Ahbijit. You're very welcome! By the way, that Personas idioms document is a collaborative document. If I got the settings right you should be able to edit it to add anything you think is appropriate. I had intended that it would become the document you are talking about. It may make sense to change the title to "Personas Best Practices" too, perhaps?
Moving on to your problems:
- Deciding whether or not something can be achieved in Personas can only really be done by trying it, at least initially. It does get easier with experience. Personas isn't the only factor here, of course. You need to know the transactions quite well also.
- After grabbing an error message from the status bar, you may be able to use a "contains" test in an IF - contains "E:" or contains "W:". That depends on the nature of the error message - not all messages are so helpfully structured! I sometimes use a "JavaScript" action to parse the message and decide between warning and error. Because the Personas script IF only tests values in screen fields, I have a hidden field into which I paste a value that can be tested.
- In your specific example of PO statuses, I've faced the same problem. I tested the final status - status 5 I think. If it was blank the ones I wanted were 1-3, if it wasn't blank they were 2-4. I don't think there's a generic solution to this sort of problem. You have to take each transaction as it comes.
- Are you using Personas SP03? Copying and pasting values in checkboxes works much better in SP03.
- Pasting into tables can be tricky, yes. You can address table cells individually but dealing with whole tables is best avoided for now.
Steve.