x Want to participate? Join the group to interact
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 13 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 2623 views
  • Users 0 members are here
Browse Forums
Announcements
106
topics
32
replies
General Discussion
6k
topics
18k
replies
Michele Gaw

Component Manager and workflow

SOLVED
Posted By

During the overhaul of an existing Sage CRM system that has been around for many years.  It was decided to abandon the current install and start from scratch on a new server with the same version.  While were were doing the customizations on the original server, we had the component manager turned on to capture the customizations.

However, when we applied the customizations on the new server, the workflows that had been created did not come over.  Is there a way that I can move these without have to recreate them from scratch?  One of the workflows is fairly simple and would not be a big deal to recreate.  However, the other one would be painful to do and I am on a tight time schedule.

Any assistance would be greatly appreciated!  Thank you! 

Parents
  • 0

    I think I figured this out with the help of this post. (This didn't come up when I was initially looking.)
    www.sagecity.com/.../copy-existing-workflow

    However, I did have to do some messing around to get it to work. Here are some things that I found I needed to do in addition to copying the workflow script into the .es file.

    1. Name everything the same for the component piece. (My workflow's name was EntityWorkflow)

    Folder = MyComponent
    .es file = MyComponent.es
    .ecf file = MyComponent.ecf

    .ecf file contained the following..
    Description=
    Directory=MyComponent
    Version=2017

    2. Set your current recording component to be the same (MyComponent). I am not sure if this is necessary. However, the system would not accept the components I was bringing over until the current recording component had the same name.

    3. If you have .asp pages in your workflow, they will need to exist in the entities directory or you will need to add them to the component.  (Again not sure about this one either...but it didn't work until they were there.)

    It appears my workflow came over and looks good on the surface. :-)

    Now I am going to try the other one which is more complicated. Fingers crossed that I have success with that one as well!

Reply
  • 0

    I think I figured this out with the help of this post. (This didn't come up when I was initially looking.)
    www.sagecity.com/.../copy-existing-workflow

    However, I did have to do some messing around to get it to work. Here are some things that I found I needed to do in addition to copying the workflow script into the .es file.

    1. Name everything the same for the component piece. (My workflow's name was EntityWorkflow)

    Folder = MyComponent
    .es file = MyComponent.es
    .ecf file = MyComponent.ecf

    .ecf file contained the following..
    Description=
    Directory=MyComponent
    Version=2017

    2. Set your current recording component to be the same (MyComponent). I am not sure if this is necessary. However, the system would not accept the components I was bringing over until the current recording component had the same name.

    3. If you have .asp pages in your workflow, they will need to exist in the entities directory or you will need to add them to the component.  (Again not sure about this one either...but it didn't work until they were there.)

    It appears my workflow came over and looks good on the surface. :-)

    Now I am going to try the other one which is more complicated. Fingers crossed that I have success with that one as well!

Children
No Data

*Community Hub is the new name for Sage City