date:20100604

Re: Deleting Remedy Records Specifically Incidents and Their Audits

2010-06-04 Thread Robert Fults

You generally don't want to delete the records.  Consider archiving them 
instead.

Robert Fults
Remedy Admin/Dev
Florida International University


From: Kevin Begosh [kbeg...@gmail.com]
Sent: Friday, June 04, 2010 2:07 PM
Subject: Deleting Remedy Records Specifically Incidents and Their Audits

**
Just wondering how everyone out there removes records, HelpDesk tickets 
specifically and it's audits from the system.  I was going to have an 
escalation that went through and remove all of the based on that cirteria, have 
a delete flag or something, but how is everything removing the Audit logs and 
for that matter all other forms related, Worklogs, SLM:Measurements etc...

Just for the audit logs though for help desk, form is 
HPD:HelpDesk_AuditLogSystem

Is the best way to in the same workflow that is deleting the helpdesk record to 
do a delete on the Audit log record if the $Original Request ID$ = 'Entry ID'

Not looking so much for a hey do this but just wondering what everyone does

--
Kevin Begosh
_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

(RESOLVED:he date format is invalid;

2010-06-04 Thread Renjini Johney

Dear all, Thanks a million for the inputs :)
As you suggested I used the below format and it worked
2010-06-04T13:11:00-07:00

Regards
Renjini



On Fri, Jun 4, 2010 at 2:41 PM, Grooms, Frederick W <
frederick.w.gro...@xo.com> wrote:

> **
>
> For Web services you have to use the XML format of a date/time
>
>
>
> From http://www.w3.org/TR/xmlschema-2/#dateTime
>
> XML defines dateTime as a finite-length sequences of characters of the
>
>form:  '-' mm '-' dd 'T' hh ':' mm ':' ss ('.' s+)? (zz)?
>
>
>
> i.e.  2010-06-04T14:40:15.000-05:00
>
> A Date Only field would use the date portion, a Time Only field would use
> the time portion
>
>
>
> Fred
>
>
>
>
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arsl...@arslist.org] *On Behalf Of *Renjini Johney
>
> *Sent:* Friday, June 04, 2010 4:18 PM
> *To:* arslist@ARSLIST.ORG
> *Subject:* ERROR (8957): The date format is invalid;
>
>
>
> **
>
> Hi All,
>
>
>
> I am trying to send a soap message to submit a incident to help desk using
> web services and i keep getting the below error,
> please let me know your inputs if someone has seen this error before.
>
> faultcode>soapenv:Server.userException
>  ERROR (8957): The date format is invalid;
> ?
>  
>
> --
> Regards,
> Renjini johney
>
>
>
>
> _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_




-- 
Regards,
Renjini johney

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Re: ERROR (8957): The date format is invalid;

2010-06-04 Thread Grooms, Frederick W

For Web services you have to use the XML format of a date/time


>From http://www.w3.org/TR/xmlschema-2/#dateTime

XML defines dateTime as a finite-length sequences of characters of the

   form:  '-' mm '-' dd 'T' hh ':' mm ':' ss ('.' s+)? (zz)?

i.e.  2010-06-04T14:40:15.000-05:00
A Date Only field would use the date portion, a Time Only field would use the 
time portion

Fred


From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Renjini Johney
Sent: Friday, June 04, 2010 4:18 PM
To: arslist@ARSLIST.ORG
Subject: ERROR (8957): The date format is invalid;

**
Hi All,

I am trying to send a soap message to submit a incident to help desk using web 
services and i keep getting the below error,
please let me know your inputs if someone has seen this error before.
faultcode>soapenv:Server.userException
 ERROR (8957): The date format is invalid; ?
 

--
Regards,
Renjini johney



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Re: ERROR (8957): The date format is invalid;

2010-06-04 Thread Lyle Taylor

Some possible things to look into that might help:


* Is the locale of the machine calling the web service different than 
the locale setting of the mit tier  or web services server?

* Is the locale of the mid-tier/web services server the same as the AR 
server (if running on different servers?

* Does the user that is authenticating to make the web service call 
have a locale specified for them?  If so, is that locale the same as the 
machine the web service is being called from?

* With all that in mind, can you verify that the code calling the web 
service is formatting the date string according to the expected format for the 
given locale(s)?

Good luck,
Lyle

From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Renjini Johney
Sent: Friday, June 04, 2010 3:18 PM
To: arslist@ARSLIST.ORG
Subject: ERROR (8957): The date format is invalid;

**
Hi All,

I am trying to send a soap message to submit a incident to help desk using web 
services and i keep getting the below error,
please let me know your inputs if someone has seen this error before.
faultcode>soapenv:Server.userException
 ERROR (8957): The date format is invalid; ?
 

--
Regards,
Renjini johney
_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_


 NOTICE: This email message is for the sole use of the intended recipient(s) 
and may contain confidential and privileged information. Any unauthorized 
review, use, disclosure or distribution is prohibited. If you are not the 
intended recipient, please contact the sender by reply email and destroy all 
copies of the original message.



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

JOB: Identity Management / Control-SA Sys Admin

2010-06-04 Thread Thad K Esser

**
Listers,

This isn't a Remedy job, but it is BMC
product related (Control-SA), so I thought I'd throw it out there in case
anyone was interested.

Don't send resumes to me, apply online:
http://www.regence.com/careers
Job # : 18153
Location: Portland, Oregon

Thanks,
Thad Esser
Remedy Developer

In this position it is essential that
IT departmental policies and procedures be adhered to. Those include, but
are not limited to technical and architecture standards, production implementation
standards, regular status reporting, regular participation in team meetings,
regular one on one meetings with supervisor and team lead, and providing
work estimates and regular time tracking.
Qualifications:
•A minimum of 3 years relevant experience,
in a multi-platform environment and multi system environment, including,
but not limited to Identity Management, UNIX administration and Web Infrastructure
Administration.
• At least 1 year experience with identity
management technologies, including, but not limited to:
• BMC Control-SA/Identity Management
Suite, Oracle Identity Manager or Sun Identity Manager
• BMC Web Access Manger/UiDP, OpenSSO,
CA Siteminder or Tivoli Access Manager
• Sun Directory Server or OpenLDAP

• Experience specifically with user
account provisioning strongly preferred.
• Must have a good understanding of
UNIX.
• Scripting in Shell, PERL, Python,
TCL etc. desired.
• General web experience including
J2EE/.NET web and application servers a plus
• Bachelors degree in Computer Science,
Mathematics, Business Administration, or a related field. Appropriate additional
experience beyond the minimum required experience may be substituted for
education.
• Must be able to develop positive
relationships among clients, coworkers and management.
• Must be able to work effectively
with other team members.
• Must be able to work with minimum
direction.
• Must be able to plan and manage his/her
own work.
• Must be able to take direction from
others in analyzing and solving program and system issues and problems.

• Must be able to analyze, diagnose
and resolve system performance problems or outages.
• Must be able to automate system programmer
tasks and document them for others to use.
• Must be able to effectively communicate
with coworkers and all levels of management.
• Must be able to effectively adapt
to rapidly changing technologies and methodologies and apply them to technological
and/or business needs.
• Must participate in on-call rotation
and be available 24x7 during the on-call rotation.

*IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.
*

44 matches

Mail list logo