Haven’t tried Delphix but it you want to create a copy of your custom 7.6.4 application you might want to try ITSM Bridge: www.itsmbridge.com
Mark Herring > On 7 May 2016, at 05:00, arslist automatic digest system > <[email protected]> wrote: > > There are 9 messages totaling 343 lines in this issue. > > Topics of the day: > > 1. Getting an email from NTE Notifications in both HTML and Plain txt > 2. CMDBBOException occurred: ERROR (120417, Unable to Create SRD (2) > 3. Making field required after the fact (5) > 4. Using ARS 7.6.4 & Delphix to create a virtual copy of our app > > The following is a DIGEST of postings to the ARSlist: > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > ---------------------------------------------------------------------- > > Date: Fri, 6 May 2016 06:48:14 -0700 > From: Kelly Deaver <[email protected]> > Subject: Re: Getting an email from NTE Notifications in both HTML and Plain > txt > > [Message contains invalid MIME fields or encoding and could not be processed] > > ------------------------------ > > Date: Fri, 6 May 2016 14:17:33 -0400 > From: Sri teja <[email protected]> > Subject: CMDBBOException occurred: ERROR (120417, Unable to Create SRD > > Help, > > Getting below error while trying to create an SRD. Any suggestions would be > really helpful ? > Remedy 8.1 > > CMDBBOException occurred: ERROR (120417): An unknown error occured > while trying to create a CMDB Relationship Instance between two of the > business objects; Class : com.bmc.atrium.bol.BORequestableOffering, Id : = > OI-6679dfb5968f4b48a644bca5ccc3ba54 ; Caused by: ERROR (120040): The > relationship endpoint instance does not exist.; > Rel(clsId:BMC.CORE:BMC_DEPENDENCY instId: OI-4b59de007fa348549c6a16711600452d > can't be created. L-endpoint inst does not exist -- , instId: > BMC_GLOBAL_DEFAULT_SRVC_OFFERING (ARERR 191005) > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > ------------------------------ > > Date: Fri, 6 May 2016 15:43:07 -0400 > From: Tom Siegel <[email protected]> > Subject: Making field required after the fact > > Folks I have a custom tab on the HPD:Help Desk form that holds a custom > DateTime field. The ask was to make the field required if the logged in user > is a member of a specific support group. Easy enough so I created an active > link to make the field required. Everything works as it should on submit, but > even though the lable is bold and has the asterisk, the system is not > treating the field as required on Modify. After doing some active link > logging I decided to disable my active link and make the field required on > the HPD:Help Desk form. Same behavior, it is enforced on submit but not on > modify. Could this perhaps be built in functionality for Remedy? If so are > there any suggested work arounds? > > Thansk, > > Tom > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > ------------------------------ > > Date: Fri, 6 May 2016 19:56:53 +0000 > From: "Grooms, Frederick W" <[email protected]> > Subject: Re: Making field required after the fact > > Are you saying the field is required each time a member of the group updates > the record or once it has a value it is good for the life of the ticket? > > Fred > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Tom Siegel > Sent: Friday, May 06, 2016 2:43 PM > To: [email protected] > Subject: Making field required after the fact > > Folks I have a custom tab on the HPD:Help Desk form that holds a custom > DateTime field. The ask was to make the field required if the logged in user > is a member of a specific support group. Easy enough so I created an active > link to make the field required. Everything works as it should on submit, but > even though the lable is bold and has the asterisk, the system is not > treating the field as required on Modify. After doing some active link > logging I decided to disable my active link and make the field required on > the HPD:Help Desk form. Same behavior, it is enforced on submit but not on > modify. Could this perhaps be built in functionality for Remedy? If so are > there any suggested work arounds? > > Thansk, > > Tom > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > ------------------------------ > > Date: Fri, 6 May 2016 21:16:29 +0100 > From: Peter Romain <[email protected]> > Subject: Re: CMDBBOException occurred: ERROR (120417, Unable to Create SRD > > Sounds like someone has deleted the default BMC_GLOBAL_DEFAULT_SRVC_OFFERING > CI from BMC_SERVICEOFFERING class in the CMDB. > > If you have another system check if it exists there and copy it to the system > causing you a problem. > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Sri teja > Sent: 06 May 2016 19:18 > To: [email protected] > Subject: CMDBBOException occurred: ERROR (120417, Unable to Create SRD > > Help, > > Getting below error while trying to create an SRD. Any suggestions would be > really helpful ? > Remedy 8.1 > > CMDBBOException occurred: ERROR (120417): An unknown error occured > while trying to create a CMDB Relationship Instance between two of the > business objects; Class : com.bmc.atrium.bol.BORequestableOffering, Id : = > OI-6679dfb5968f4b48a644bca5ccc3ba54 ; Caused by: ERROR (120040): The > relationship endpoint instance does not exist.; > Rel(clsId:BMC.CORE:BMC_DEPENDENCY instId: OI-4b59de007fa348549c6a16711600452d > can't be created. L-endpoint inst does not exist -- , instId: > BMC_GLOBAL_DEFAULT_SRVC_OFFERING (ARERR 191005) > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "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" > > ------------------------------ > > Date: Fri, 6 May 2016 16:33:53 -0400 > From: Tom Siegel <[email protected]> > Subject: Re: Making field required after the fact > > Fred - Once the field has a value, it is good for the life of the ticket > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > ------------------------------ > > Date: Fri, 6 May 2016 15:29:01 -0500 > From: Brad Fike <[email protected]> > Subject: Using ARS 7.6.4 & Delphix to create a virtual copy of our app > > All, > > My current client has a completely custom 7.6.4 application. > On Unix & Oracle. > > They also purchased Delphix about a year ago but do not have any in-house > expertise and I have never used the product. Our goal is to use Delphix to > create a virtual "snapshot" of the 7.6.4 application to use as a demo > environment. > > Has anyone out there had any experience with Delphix that they would be > willing to share with me? > > Thanks, > Brad Fike > [email protected] > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > ------------------------------ > > Date: Fri, 6 May 2016 16:50:40 -0400 > From: Tom Siegel <[email protected]> > Subject: Re: Making field required after the fact > > I think I have part of it figured out. It appears that if you change an > existing field from optional to required the functionality is as follows > 1) The required field will be enforced on create and an error message will > display > 2) If you open an exisiting incident with the newly required field blank but > change another field and submit (modify). The system will not enforce the > field requirement > 3) If you open an existing incident, populate the required field, > submit(Modify), clear the required field, submit(Modify). The required field > will be enforced on submit and an error message will display > > I will try this again with my active link, If I can't get this functionality > I will use the active link to make the field label bold, and use a filter to > enforce the field being populated (required) on create and modify > > Thanks, > > Tom > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > ------------------------------ > > Date: Fri, 6 May 2016 20:57:47 +0000 > From: "Mueller, Doug" <[email protected]> > Subject: Re: Making field required after the fact > > Tom, > > The enforcement of required is working correctly... You just need to > understand what is happening on Modify. > > The way a Modify works from our UI is that we send only CHANGED fields. That > means you are not modifying the date field in question so there is no > checking whether there is a value or not. So, there is no enforcement. If > you tried to blank the field on an existing record, you would find that the > system would complain about a missing required field. > > If you want to force the entry of a missing date on an existing entry, you > need to put something to force that. I would suggest you do that on the > client or you will have problems with automated processes that may be > updating the record suddenly getting errors and I don't think you want that. > > What you would do is for this field that you have newly made required, is put > an active ink that fires on Modify (so it runs only on the modify operation > as Create is covered already) with a run if of 'field' = $NULL$ and an > Action of Error and a message that tells the user that they must fill in a > date. NOW, the user that is trying to modify will be forced to enter a date > for the date field if it is empty or they will not be able to modify. Any > record with the field filled in will not trigger this workflow. > > So, this is how you would do what you are asking. Note however that this is > a bit harsh. That means that ANY USER coming along who wants to modify > anything about one of these records without a date MUST supply a date before > they will be allowed to save anything to the record. > > Doug > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Tom Siegel > Sent: Friday, May 06, 2016 1:51 PM > To: [email protected] > Subject: Re: Making field required after the fact > > I think I have part of it figured out. It appears that if you change an > existing field from optional to required the functionality is as follows > 1) The required field will be enforced on create and an error message will > display > 2) If you open an exisiting incident with the newly required field blank but > change another field and submit (modify). The system will not enforce the > field requirement > 3) If you open an existing incident, populate the required field, > submit(Modify), clear the required field, submit(Modify). The required field > will be enforced on submit and an error message will display > > I will try this again with my active link, If I can't get this functionality > I will use the active link to make the field label bold, and use a filter to > enforce the field being populated (required) on create and modify > > Thanks, > > Tom > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "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" > > ------------------------------ > > End of arslist Digest - 5 May 2016 to 6 May 2016 (#2016-104) > ************************************************************ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
