Crude/thin, but we use a Request For Enhancement form, which describes
business reasons for change. We use form Change History to document the
specific changes (For RFE #999, <change details>). Summary reporting is
done from the RFE form, break-fix support reference documentation is
provided by Change History
We also use Panacea Workflow Studio and can cross-reference the changes
(search Change History for "For RFE #999" to identify all objects created
or updated on behalf of a particular RFE).
Change history is "what" was done, RFE is "why" it was done.
Mike White
Office: 813-978-2192
E-mail: [EMAIL PROTECTED]
William Rentfrow
<[EMAIL PROTECTED] To: [email protected]
COMINC.COM> cc:
Sent by: "Action Subject: Re: Documentation -
Workflow, etc.
Request System
discussion
list(ARSList)"
<[EMAIL PROTECTED]
ORG>
03/20/2008 11:19
Please respond to
arslist
I'd have to agree - having just the form in Remedy (whichever way you do
it) is a good start but you have to have something that ties the project
together for the build. Specifically something like "We did this workflow
customization to support this process which fulfills this functional
requirement".
William Rentfrow
Principal Consultant, StrataCom
[EMAIL PROTECTED]
O 952-432-0227
C 701-306-6157
________________________________
From: Action Request System discussion list(ARSList) on behalf of Rick Cook
Sent: Thu 3/20/2008 10:11 AM
To: [email protected]
Subject: Re: Documentation - Workflow, etc.
** One thing you could do, Ty, is to create a form and workflow that uses
Server Events (v7) to track when new forms and workflow objects are created
and modified. Then you could run reports off of that form. Took me a
couple days to build mine.
Add to that design docs, etc. as others have mentioned.
Rick
On Thu, Mar 20, 2008 at 7:33 AM, T. Dee <[EMAIL PROTECTED]> wrote:
I was kind of thinking of writing a Form in Remedy to track
all my
changes, but wanted to see how others are doing it.
On 3/20/08, William Rentfrow <[EMAIL PROTECTED]>
wrote:
> We're kind of undertaking that exercise right now. We are
producing the "build doc" for this project. It has all customizations,
configuration, etc, we did - literally any change that was performed to the
system after the basic server/application install was complete (including
licensing, etc).
>
> Last I looked we were near 100+ page mark and growing. The
30 pages that are sideways with 8 point font showing workflow
customizations are a REAL joy to read :)
>
> William Rentfrow
> Principal Consultant, StrataCom
> [EMAIL PROTECTED]
> O 952-432-0227
> C 701-306-6157
>
> ________________________________
>
> From: Action Request System discussion list(ARSList) on
behalf of Moore, Christopher Allen
> Sent: Thu 3/20/2008 9:07 AM
> To: [email protected]
> Subject: Re: Documentation - Workflow, etc.
>
>
>
> Not really documentation, but something I think is a good
practice we do
> here- if we need to alter workflow that was OOTB, after we
make our
> change to it we do a 'Save As...' and add a prefix to be
beginning of
> the workflow name, and deactivate the old workflow.
>
> That way we can easily roll back any changes.
>
> Chris
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of T. Dee
> Sent: Thursday, March 20, 2008 8:20 AM
> To: [email protected]
> Subject: OT: Documentation - Workflow, etc.
>
> I was wondering for those of you who do customizations,
modifications,
> etc., how do you document your changes / workflow, etc.
>
> Thanks!
>
>
________________________________________________________________________
> _______
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <
http://www.arslist.org/>
> Platinum Sponsor: www.rmsportal.com <
http://www.rmsportal.com/> ARSlist: "Where the Answers Are"
>
>
_______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <
http://www.arslist.org/>
> Platinum Sponsor: www.rmsportal.com <
http://www.rmsportal.com/> ARSlist: "Where the Answers Are"
>
>
_______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <
http://www.arslist.org/>
> Platinum Sponsor: www.rmsportal.com <
http://www.rmsportal.com/> ARSlist: "Where the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <
http://www.arslist.org/>
Platinum Sponsor: www.rmsportal.com <http://www.rmsportal.com/
> ARSlist: "Where the Answers Are"
__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
html___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
