Project naming convention

How to configure project naming convention so we can migrate the same project definition name from source to target environments including the project definition properties and comments? For example РWhen developers create a PeopleSoft project and they need to update the Project definition properties (who, when, incident number, what changes or why its need etc). We need to migrate same project definition (including properties) to other environments.

3 Comments »

  1. Admin said,

    October 20, 2016 @ 12:46 pm

    You may have seen that Phire generates its own project when performing the migrations. The name of that project is noted on the Migrations tab and it would contain all of the objects included in the migration set being migrated. This is done because a developer may or may not load the entire contents of their project from App Designer, or they may combine multiple projects into one CR, or they may have no project whatsoever.

    So I think your question is referring to that original project the developer uses, and that you’d like that project moved into the target(s) along with all of the objects it contains. This can be done by a simple checkbox at the point where the developer imports the project – you’ll see a checkbox labeled “Include Project Object”. By checking this, the developer’s project will be added to the list of objects and included in the migration to the target(s).

    If you would like, that “Include Project Object” checkbox can be checked by default by a simple setting in the Define Domain configuration page. With that, the developer won’t need to remember to check it and it will always include the original project.

    If you have any further questions about this aspect of Phire, please contact us in Support for a detailed look at your requirements. support@phire-soft.com

  2. Pradip said,

    October 24, 2016 @ 7:28 pm

    Thanks for your reply Admin.
    Is there any way to stop Phire Generated Projects do not migrate to target environments? We want only original development should migrate to target environments specially PROD and UAT.

  3. Admin said,

    November 17, 2016 @ 10:08 am

    There is not an option to suppress the Phire-generated project.

    The purpose has been to document in an App Designer project exactly what was migrated given that it may be different than the original project as described above. These projects are generally easy to identify with the naming convention and ignored for reporting or queries that you might use.

    If you have a specific problem that this is causing, then I suggest you contact support at support@phire-soft.com to discuss your particular requirements.

RSS feed for comments on this post · TrackBack URI

Leave a Comment

You must be logged in to post a comment.