Hi Ryan\David, I
> > > ** > > Hi David,**** > > ** ** > > Can you delete the “placeholder” form? It appears this particular > placeholder form is corrupt. As you stated…even placeholder forms require a > name.**** > > ** ** > > Do you know what imported workflow would have created the placeholder form? > **** > > ** ** > > As an FYI:**** > > ** ** > > Importing shared workflow not owned by the application**** > > When you import an application definition file that contains shared > workflow not owned by the application, AR System can create a > non-functional *placeholder form* > > for each external form associated with the shared workflow. This allows > developers to modify the shared workflow owned by another application > without installing the integrated application on the development server. It > also ensures that the complete list of associated forms is preserved with > any shared workflow.**** > > Placeholder forms are created during application import in these cases:*** > * > > **· **The import definition contains shared workflow from another > application that**** > > includes a Push Fields or Set Fields action. In this case, a placeholder > is created for the external form used by the Push Fields or Set Fields > action.**** > > **· **The server configuration file (ar.cfg or ar.conf) contains > the option Create-Workflow-Placeholders: T. In this case, a placeholder > form is created for any external form associated with the shared workflow, > regardless of the workflow action type.**** > > A placeholder form has no fields and can only be deleted. If the actual > definition of a placeholder form is imported, it replaces the existing > placeholder. In the Forms object list in BMC Remedy Developer Studio, > placeholder forms are identified as form type “None”. When importing an > application definition that contains shared workflow not owned by the > application, the workflow object is created if it does not already exist. > If the workflow object already exists, only the list of associated forms is > updated. If the application that owns the shared workflow object is later > imported, the workflow is replaced.**** > > ** ** > > If the placeholder form can be deleted then I am hoping at that point you > can create/save other forms.**** > > ** ** > > Regards,**** > > Ryan.**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Longwing, Lj > *Sent:* Tuesday, April 16, 2013 2:00 PM > > *To:* [email protected] > *Subject:* Re: Question related to placeholder forms**** > > ** ** > > ** **** > > Ok, in that scenario, I can guarantee you that another form isn't at play. > To be able to help we will need the actual message that you are receiving, > including error number, and if you could also turn on SQL Logging on the > server before you do the save, and include the relevant portions of the log > with the reply, that would also help.**** > > ** ** > > On Tue, Apr 16, 2013 at 11:43 AM, Drake, David <[email protected]> > wrote:**** > > ** **** > > Dev Studio**** > > **** > > *David Drake***** > > *Application Systems Analyst***** > > *ITSM Application Support** > Koch Business Solutions, LP** ***** > > *email: *david.drake@*kbslp.com* <[email protected]>* | **office: > 316-828-6113**| **cell: 316-200-1991***** > > *Error! Filename not specified.* <http://myitsupport/>* ***** > > **** > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Longwing, Lj > *Sent:* Tuesday, April 16, 2013 12:20 PM > *To:* [email protected] > *Subject:* Re: Question related to placeholder forms**** > > **** > > ** By save, do you mean in dec studio or client?**** > > > > On Tuesday, April 16, 2013, Drake, David <[email protected]> wrote: > > ** > > > > Need to see if anyone has any insight into the probable cause and/or fix > for the following > > > > > > > > We’re no longer able to save any kind of forms. The error indicates that > the fields cannot be found. This is on a brand new regular form and the > core fields are right there so the error is coming from some other form > that is being accessed when saving this form. We have found a placeholder > form but it doesn’t have a name (even though that’s a required field) and > we suspect that may be the culprit. Has anyone any insight into this or > something similar? Thanks! > > > > > > > > ITSM 7.6.04 SP2, SQL2K5, Windows Server > > > > > > > > David Drake > > > > Application Systems Analyst > > > > ITSM Application Support > > Koch Business Solutions, LP > > > > email: [email protected] | office: 316-828-6113| cell: 316-200-1991 > > > > > > > > > >**** > > > _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_ **** > > ** ** > > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > > > -- > Thanks and Regards, > Sagar Valse > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
