Prev
Next
Forums User Experience Lawson Design Studio

Food for thought

 1 Replies
 0 Subscribed to this topic
 12 Subscribed to this forum
Sort:
Author
Messages
Terry P
Veteran Member
Posts: 234
Veteran Member
11/16/2009 9:37 PM

    Let me start out by saying I am not (any longer) a COBOL or RPG programmer. I don't have access to the code to make changes. I think however I've gotton pretty good at using Design Studio's scripting feature to make pretty extensive changes to a form (knowing all to well the risk you take)

    After a recent project where I was able to extensively modify a form that was designed for one purpose, and used for another, it got me to thinking - If a generic form was written that ONLY did read/write between the form and the table, you could use Design Studio to build your user interface, edits, and certain amount of program logic. All your "back end" program would need to do is add, change, delete, inquire on the table.

    I'd like to hear from some of you programmer types what you think about this?

    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
    11/17/2009 12:44 PM
      Terry - the concept is a good one and I've done this to a point. I've taken the WFWK forms and used them as blank pallets to create customizations to do ProcessFlow administration. That way clients can access a form that allows approvers to set up vacation coverage and quasi-administrators the ability to add or delete approvers (and keep them out of ProcessFlow Administration menu.do).

      I also taken one form and redisigned it to do the work of two seperate forms (AR09 & AR10, for example) but don't disagree that it might sometimes have been easier to start with a blank form and build it to do all of the functions that I needed.
      David Williams