• State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 17 subscribers
  • Views 14426 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Stat Environment Refresh

mullenje
over 7 years ago

I'm looking at the Stat functionality to record Environment Refreshes.  I'm confused why an environment refresh would be tied to a specific CSR.  If env1 is refreshed from env2, it impacts any CSRs which migrated objects to env2, but to see details on a refresh event or make changes to the refresh event, I need to go into that specific CSR I entered the env refresh info into?  How do most people use this functionality?  Should there be a separate CSR Type for tracking Environment Refreshes?

Parents
  • 0 over 7 years ago
    I would be curious in the thoughts of other customers as there may be many ideas here. From my point of view, I always thought a specific CSR type was appropriate as the workflow would be unique and the approvals would be very special. While their could be deviations between environments, i.e. PROD-> Dev might be very different from PROD->Training from an approval point of view or even from a frequency point of view. I also think the approvals would be different as the impact of a refresh may be much greater than one team or area. Creating this workflow wouldn't be that major of a task but would allow a more specific and typically shorter process for approval.
Reply
  • 0 over 7 years ago
    I would be curious in the thoughts of other customers as there may be many ideas here. From my point of view, I always thought a specific CSR type was appropriate as the workflow would be unique and the approvals would be very special. While their could be deviations between environments, i.e. PROD-> Dev might be very different from PROD->Training from an approval point of view or even from a frequency point of view. I also think the approvals would be different as the impact of a refresh may be much greater than one team or area. Creating this workflow wouldn't be that major of a task but would allow a more specific and typically shorter process for approval.
Children
No Data