My application have 3 buttons.They are named collection,supension and resume.
The process is as follows.
1.put the account in collection and confirm the account in collection
2.Then suspend the account
3.Then Resume the service.
Situation:I can put the account only once in collection after that the button is disabled.So Next time i cannot click the collection button since it is disabled.I can do the suspend and resume infinite number of times.
Some accounts are already in collection and some accounts are not.If it is not in collection,i have to put the account in collection and do the commit operation.If it is in collection i have to do only suspend and Resume so i skip the collection operation.
I recorded the script by first putting the account in collection ,and suspend the account and resume the account.
My script is working fine.But when i want to rerun the script ,it is failing.The reason is that the collection button is now disabled.so my script is aborted.
I need some tips to resolve this problem.Suppose when i rerun the script,the script should check whether the collection button is disabled or not.If the collection button is visible it should do the collection operation otherwise the script
should skip collection operation and continue with suspend and resume operation.
Is there any way you can check the status of the account when you retrieve it (is the status being returned by the server?)? If so, you could also add custom logic to make the script smart enough to know when to do the collection and when not to.
SoCalGal - Defender of end user response times!