Re: Question related to placeholder forms

2013-06-14 Thread Sagar Valse
Hi Ryan,

Thanks a lot!!!
The issue got resolved.The blank placeholder was there in the database.
Just wondering how the blank placeholder got created.


On Thu, Jun 13, 2013 at 6:59 PM, Downing, Ryan ryan_down...@bmc.com wrote:

 **

 Hi Sagar,

 ** **

 You said you “tried” deleting the blank placeholder. Did it delete? Or did
 you get the error when you tried to delete?

 ** **

 Perform the following SQL query:

 ** **

 select name,schemaId from arschema

 ** **

 You should not have any entries in the arschema form with a NULL name
 value. If you do have any entries with a NULL value try the following:

 ** **

 **1.   **BACKUP your database

 **2.   **Delete the entry or entries in arschema where the name is
 NULL

 **3.   **Now try and create/modify/delete on any other form

 ** **

 Hopefully this will allow you to save/modify other forms…..

 ** **

 I hope this helps,

 ** **

 Regards,

 Ryan.

 ** **

 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Sagar Valse
 *Sent:* Thursday, June 13, 2013 5:24 AM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Fwd: Question related to placeholder forms

 ** **

 ** 

 ** **

  Hi Ryan\David,
  

 I am facing similar issue and i tried deleting the blank placeholder as
 well.

 But still i was getting same error.

 Did you got any solution for issue.

 Thanks and Regards,
 Sagar Valse 



 ** 

 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:
 arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
 *Sent:* Tuesday, April 16, 2013 2:00 PM


 *To:* arslist@ARSLIST.ORG
 *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 david.dr...@kbslp.com
 wrote:

 ** 

 Dev Studio

  

 *David Drake*

 *Application Systems Analyst*

 *ITSM Application Support**
 Koch Business Solutions, LP** *

 *email: *david.drake@*kbslp.com* david.dr...@kbslp.com* | **office:
 316-828-6113**| **cell: 316-200-1991*

 *Error! Filename not specified.* http://myitsupport/* *

  

 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
 *Sent:* Tuesday, April 16, 2013 12:20 PM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Re

Re: Question related to placeholder forms

2013-06-14 Thread Downing, Ryan
Hi Sagar,

I am glad to see that this resolved your issue  :)

Unfortunately, I cannot tell you how the entry became corrupt to begin with. 
During the import of workflow that referenced a form that did not existan 
entry was created in arschema to allow for the import of associated workflow. 
Somehow the name got NULL'ed out   :(

Anyways, glad to hear you are again up and running.

Regards,
Ryan.

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Sagar Valse
Sent: Friday, June 14, 2013 2:41 AM
To: arslist@ARSLIST.ORG
Subject: Re: Question related to placeholder forms

**
Hi Ryan,
Thanks a lot!!!
The issue got resolved.The blank placeholder was there in the database.
Just wondering how the blank placeholder got created.

On Thu, Jun 13, 2013 at 6:59 PM, Downing, Ryan 
ryan_down...@bmc.commailto:ryan_down...@bmc.com wrote:
**
Hi Sagar,

You said you tried deleting the blank placeholder. Did it delete? Or did you 
get the error when you tried to delete?

Perform the following SQL query:

select name,schemaId from arschema

You should not have any entries in the arschema form with a NULL name value. If 
you do have any entries with a NULL value try the following:


1.   BACKUP your database

2.   Delete the entry or entries in arschema where the name is NULL

3.   Now try and create/modify/delete on any other form

Hopefully this will allow you to save/modify other forms.

I hope this helps,

Regards,
Ryan.

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Sagar 
Valse
Sent: Thursday, June 13, 2013 5:24 AM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: Fwd: Question related to placeholder forms

**

 Hi Ryan\David,

I am facing similar issue and i tried deleting the blank placeholder as well.
But still i was getting same error.
Did you got any solution for issue.
Thanks and Regards,
Sagar Valse


**
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:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, 
Lj
Sent: Tuesday, April 16, 2013 2:00 PM

To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
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 
david.dr...@kbslp.commailto:david.dr...@kbslp.com wrote:
**
Dev Studio

David Drake
Application Systems Analyst
ITSM Application Support
Koch Business Solutions, LP
email: david.dr...@kbslp.commailto:david.dr...@kbslp.com | office: 
316-828

Re: Question related to placeholder forms

2013-06-13 Thread Sagar Valse
 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:
 arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
 *Sent:* Tuesday, April 16, 2013 2:00 PM

 *To:* arslist@ARSLIST.ORG
 *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 david.dr...@kbslp.com
 wrote:

 ** 

 Dev Studio

  

 *David Drake*

 *Application Systems Analyst*

 *ITSM Application Support**
 Koch Business Solutions, LP** *

 *email: *david.drake@*kbslp.com* david.dr...@kbslp.com* | **office:
 316-828-6113**| **cell: 316-200-1991*

 *Error! Filename not specified.* http://myitsupport/* *

  

 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
 *Sent:* Tuesday, April 16, 2013 12:20 PM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Re: Question related to placeholder forms

  

 ** By save, do you mean in dec studio or client?



 On Tuesday, April 16, 2013, Drake, David david.dr...@kbslp.com 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: david.dr...@kbslp.com | 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

Fwd: Question related to placeholder forms

2013-06-13 Thread Sagar Valse
 Hi Ryan\David,

I am facing similar issue and i tried deleting the blank placeholder as
well.
But still i was getting same error.
Did you got any solution for issue.

Thanks and Regards,
Sagar Valse



 **

 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:
 arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
 *Sent:* Tuesday, April 16, 2013 2:00 PM

 *To:* arslist@ARSLIST.ORG
 *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 david.dr...@kbslp.com
 wrote:

 ** 

 Dev Studio

  

 *David Drake*

 *Application Systems Analyst*

 *ITSM Application Support**
 Koch Business Solutions, LP** *

 *email: *david.drake@*kbslp.com* david.dr...@kbslp.com* | **office:
 316-828-6113**| **cell: 316-200-1991*

 *Error! Filename not specified.* http://myitsupport/* *

  

 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
 *Sent:* Tuesday, April 16, 2013 12:20 PM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Re: Question related to placeholder forms

  

 ** By save, do you mean in dec studio or client?



 On Tuesday, April 16, 2013, Drake, David david.dr...@kbslp.com 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: david.dr...@kbslp.com | 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

Re: Question related to placeholder forms

2013-06-13 Thread Downing, Ryan
Hi Sagar,

You said you tried deleting the blank placeholder. Did it delete? Or did you 
get the error when you tried to delete?

Perform the following SQL query:

select name,schemaId from arschema

You should not have any entries in the arschema form with a NULL name value. If 
you do have any entries with a NULL value try the following:


1.   BACKUP your database

2.   Delete the entry or entries in arschema where the name is NULL

3.   Now try and create/modify/delete on any other form

Hopefully this will allow you to save/modify other forms.

I hope this helps,

Regards,
Ryan.

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Sagar Valse
Sent: Thursday, June 13, 2013 5:24 AM
To: arslist@ARSLIST.ORG
Subject: Fwd: Question related to placeholder forms

**

 Hi Ryan\David,

I am facing similar issue and i tried deleting the blank placeholder as well.
But still i was getting same error.
Did you got any solution for issue.
Thanks and Regards,
Sagar Valse


**
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:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, 
Lj
Sent: Tuesday, April 16, 2013 2:00 PM

To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
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 
david.dr...@kbslp.commailto:david.dr...@kbslp.com wrote:
**
Dev Studio

David Drake
Application Systems Analyst
ITSM Application Support
Koch Business Solutions, LP
email: david.dr...@kbslp.commailto:david.dr...@kbslp.com | office: 
316-828-6113tel:316-828-6113| cell: 316-200-1991tel:316-200-1991
Error! Filename not specified.http://myitsupport/

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, 
Lj
Sent: Tuesday, April 16, 2013 12:20 PM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: Re: Question related to placeholder forms

** By save, do you mean in dec studio or client?


On Tuesday, April 16, 2013, Drake, David 
david.dr...@kbslp.commailto:david.dr...@kbslp.com 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

Re: Question related to placeholder forms

2013-04-16 Thread Longwing, Lj
By save, do you mean in dec studio or client?

On Tuesday, April 16, 2013, Drake, David david.dr...@kbslp.com 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: david.dr...@kbslp.com | office: 316-828-6113| cell: 316-200-1991





 _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


Re: Question related to placeholder forms

2013-04-16 Thread Drake, David
Dev Studio

David Drake
Application Systems Analyst
ITSM Application Support
Koch Business Solutions, LP
email: david.dr...@kbslp.commailto:david.dr...@kbslp.com | office: 
316-828-6113| cell: 316-200-1991
[cid:image001.jpg@01CE3A9F.FE2A5000]http://myitsupport/

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, Lj
Sent: Tuesday, April 16, 2013 12:20 PM
To: arslist@ARSLIST.ORG
Subject: Re: Question related to placeholder forms

** By save, do you mean in dec studio or client?

On Tuesday, April 16, 2013, Drake, David 
david.dr...@kbslp.commailto:david.dr...@kbslp.com 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: david.dr...@kbslp.commailto:david.dr...@kbslp.com | 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_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years
inline: image001.jpg

Re: Question related to placeholder forms

2013-04-16 Thread Longwing, Lj
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 david.dr...@kbslp.comwrote:

 **

 Dev Studio

 ** **

 *David Drake*

 *Application Systems Analyst*

 *ITSM Application Support**
 Koch Business Solutions, LP** ***

 *email: *david.drake@*kbslp.com* david.dr...@kbslp.com* | **office:
 316-828-6113**| **cell: 316-200-1991*

 [image: cid:image002.jpg@01CDDC32.BADAA820] http://myitsupport/* *

 ** **

 *From:* Action Request System discussion list(ARSList) [mailto:
 arslist@ARSLIST.ORG] *On Behalf Of *Longwing, Lj
 *Sent:* Tuesday, April 16, 2013 12:20 PM
 *To:* arslist@ARSLIST.ORG
 *Subject:* Re: Question related to placeholder forms

 ** **

 ** By save, do you mean in dec studio or client?


 On Tuesday, April 16, 2013, Drake, David david.dr...@kbslp.com 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: david.dr...@kbslp.com | 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_


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years


Re: Question related to placeholder forms

2013-04-16 Thread Downing, Ryan
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:arslist@ARSLIST.ORG] On Behalf Of Longwing, Lj
Sent: Tuesday, April 16, 2013 2:00 PM
To: arslist@ARSLIST.ORG
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 
david.dr...@kbslp.commailto:david.dr...@kbslp.com wrote:
**
Dev Studio

David Drake
Application Systems Analyst
ITSM Application Support
Koch Business Solutions, LP
email: david.dr...@kbslp.commailto:david.dr...@kbslp.com | office: 
316-828-6113| cell: 316-200-1991
Error! Filename not specified.http://myitsupport/

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, 
Lj
Sent: Tuesday, April 16, 2013 12:20 PM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: Re: Question related to placeholder forms

** By save, do you mean in dec studio or client?


On Tuesday, April 16, 2013, Drake, David 
david.dr...@kbslp.commailto:david.dr...@kbslp.com 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: david.dr...@kbslp.commailto:david.dr...@kbslp.com | 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_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years