Just out of curiosity, in Example #2, does ARSmarts also look for table fields that might use the field in a qualification?
On Fri, Jan 30, 2015 at 7:56 AM, Support <[email protected]> wrote: > ** > Hello List, > > As I said in my previous email, here are a couple of examples that show > how ARSmarts can save you time. I realize it became quite long, but I hope > it is detailed enough. Don't hesitate to ask questions or give feedback. > > *Example 1*: find a Display-Only Character field that I can re-use. > > I need to add workflow to a Form that already has a lot of fields. I > would like to avoid the creation of yet one more Display-Only Character > field because I think that there must be one that I can re-use. > > Using Dev Studio, I cannot easily list all the Display-Only Character > fields. So I go to the zTmp.... fields, find the Character ones, and open > them one by one to check that they are Read-Only. > When I open such a field, I can list the workflow that interact with that > field (Relationships). However, I cannot see the Firing Order, which is > key information to decide whether I can re-use it or not, and if yes, what > Firing Order I have to give to my workflow. This means that I have to open > all the AL or all the Filters interacting with the Field to see what their > Firing Order is. > > Using ARSmarts, I go Navigate --> Show Objects and I select the Form. A > Form with plenty of fields, remember. > Then I list the Character, Read-Only Fields. > Then based on the name, I pick what I think could be a good candidate. > I open the Field, and in the Cross Refs tab, I see all the workflow > interacting with the field, including Firing Order, Run If condition, > summary of If and Else actions, whether they are enabled and the Execute > On. I can decide there and then if the Field can be re-used or not, > without opening all the objects. > > *Example 2*: Add a Status value to ThisForm. > > Working on a custom app that grew through the years, the customer asks > that a value be added to the Status field. The current Status values are > New - Current - Obsolete, the customer now needs New - Current - On hold - > Obsolete. The numerical values of the current Status are 0, 1 and 2 (as > you would have guessed .....). This means that I have to find all the > workflow that somehow uses the Closed value of the Status field (in Run If, > Push Field, Set Field, ....) so that I can modify each object accordingly. > > In Dev Studio: > Open the Form. > Open the Status Field. > Show Relationships. I have 150 objects that I have to check one by one. > > In ARSmarts: > Select ThisForm in the main ARSmarts window. > Search for Field with Field ID = 7. You get the Status Field. > Then, in the Previous Results tab on the Search screen, select Search in > XRefs. This will search in the cross refs of the objects found by the > previous search operation. > Still in the Search window, indicate that you want to search in the Run > If, Set Field If, Set Field, Push Field If, Push Field, ... of the Filters, > AL, Escalations. > Indicate also that you are now searching for the word Closed. > This brings me 5 objects that I can open and check. > > Note that the result of the above ARSmarts operation could also bring > "parasite" objects. For example, an AL that fires on Status, does a Set > Field and sets a field called zTmpCloseParent would also appear in the > result while it does not interact with the value Closed of the Status > field. But still, there are not many of those, and this is much, much > faster than going through all the workflow attached to Status. > > Also, to be really certain, I would in the same way look for the value > Current, just in case there is something like .... 'Status' > "Current". > > *Nice to have*: > > It is always possible to Document (in one click) the result of an > operation (Search, Compare, ....). ARSmarts will generate a nice looking > document. In most situations, you can choose between Summary or Detailed > documentation. > > It is also always possible to export the result of an operation to a .def > file (for later reference, to import on another server, as a backup, ....). > > Thank you to those who read me this far, and once again, I am open to > questions. > > Best regards, > > Kaïs. > > > On 28/01/2015 08:58, Jason Miller wrote: > > ** > Ok Kaïs, you opened the door so I'll bite :) > > The email doesn't say what functionality of ARSmarts helped save so much > time. I could easily say something like "it use to take 10 minutes for my > car to get to the end of the block but now my car can take me to the end of > the block in 30 seconds;" that is now that I am starting the engine vs. > pushing it. > > For a community of technical people I think the vagueness is almost > offensive. Give us some details. We still don't know what the customer > does with ARSmarts or what they find the most interesting. Tell us more > than some key quote snippets. > > Jason > > On Tue, Jan 27, 2015 at 7:43 AM, Support <[email protected]> wrote: > >> ** >> Hello List, >> >> I was asking to a customer what they do with ARSmarts, what functionality >> they find the most interesting, ..... and I would like to share some of >> his answer with you :-) ... >> >> " >> >> *... there was an issue in pilot testing. It took me maybe 2 minutes to >> find it with ARSmarts, while it would have been at least half an hour with >> Dev Studio." "* >> >> *Using ARSmarts saves us untold hours. ARSmarts has simply become vital >> to saving us time so we can do more." *Don't hesitate to contact me if >> you also want to do more with your time.... Or if your manager wants you to >> do more with your time ;-) :-). >> >> Cheers, >> >> Kaïs. >> [email protected] >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"

