Yes I did think of the shared workflow too which is why I did say form(s)
instead of just form in my original posting on the initial mail on this
thread.

While its OK to have fewer fields in the set field or push field mappings on
secondary forms, its not OK to have ghost fields to be a part of
qualifications in either the Run If or the Set Field IF or Push Field If
qualifications.. That qualification will just never equate to true with
fields missing in the qualification. Also, shouldn't the primary form to
which shared workflow is tied to, have all the mapping fields in the set or
push fields actions present on the form?

Instead of just removing references from existing workflow during a field
delete operation, there should have been a check during a field deletion to
disallow the operation if this field reference existed in any workflow
qualifications. It would also have been nice to have the option of having
the user prompted with names of workflow that had these references..

This is me thinking out loud.. Having this check would not be database
intensive, IF the meta table field holding the field information (field) or
any other of its related table held a flag for the field to not be deleted
the moment it was added to any qualification. This flag once added, would be
cleared only if all such references to this field was removed from
qualifications in AL's Filters, Menus, Table Field qualifications..

Joe
  -----Original Message-----
  From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Robert Molenda
  Sent: Friday, February 08, 2008 9:20 PM
  To: [email protected]
  Subject: Re: OTB ITSM Applications version 7.x


  **
  one statement:

  Shared Workflow with the Same Field ID...

  if only all of the object.references.were.object.orientated.

  ie: in the qualification fields how simple would it be to store
Form.FieldID (Form<dot>fieldid)
  ie: in the set fields - let us just remove ANY reference to fieldID X..
(that would be the un-patched version :) )

  have you ever wondered about that??

  Certainly a few more characters commmming back from the database would
assist the Object.Parse(something) function wouldn'it?

  Or, when is 8X beta coming out with a true IDE (Eclipse?) David??

  IMHO-Robert

  On Feb 8, 2008 2:14 PM, Joe D'Souza <[EMAIL PROTECTED]> wrote:

    True about it already being terribly slow..

    I'm not sure about it not causing any impact.. It would not if it is in
the
    Set Field list..

    But what if the deleted field reference exists in the Set Field If or
Push
    Field If condition. Or the Run If conditions?

    Joe


    -----Original Message-----
    From: Action Request System discussion list(ARSList)
    [mailto:[EMAIL PROTECTED] Behalf Of Axton
    Sent: Friday, February 08, 2008 4:22 PM
    To: [email protected]
    Subject: Re: OTB ITSM Applications version 7.x


    Because it would make it more horribly slow than it already is and there
is
    zero impact (aside from the admin tool meassage) to leaving it in place.

    Axton Grams

    On Feb 8, 2008 4:13 PM, Joe D'Souza <[EMAIL PROTECTED]> wrote:
    > **
    >
    > If you run the sync operation and check the arxref.log file after the
sync
    > completes or fails (fails more often than completes), you will notice
    there
    > are number of workflow objects like AL's, Filters or Menus tied to
fields
    > that have been deleted on the underlying form(s)...
    >
    > Anyone on the list who has gone through the process of correcting this
by
    > removing these 'ghost' field references from the affected workflow?
Are
    > there any available utilities that can trace such workflow and correct
    them?
    >
    > I WONDER why the ARS Admin tool wasn't designed to do this
automatically
    > when a field was deleted from a form by taking off the references to
all
    its
    > related workflow..
    >
    > Cheers
    >
    >
    > Joe D'Souza
    > Remedy Developer / Consultant,
    > Shyle Networks,
    > New Jersey.
    > Cell: +1.732.331.5004
    > Desk: +1.732.698.7275
    >
    >   __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers
Are"
    > html___


    No virus found in this outgoing message.
    Checked by AVG Free Edition.
    Version: 7.5.516 / Virus Database: 269.19.21/1266 - Release Date:
2/8/2008
    10:06 AM



    ________________________________________________________________________
_______
    UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
    Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"


  __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.19.21/1267 - Release Date: 2/8/2008
8:12 PM

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to