How to move an application from dev to prod with pipelines

[F_bio Santos]

I want to move an app from my dev instance to my prod instance, the pipelines are setup, but when I "Submit" or "Publish" the app it does not appear on the "App Managment Studio". When I "submit" my app it doesnt create a "Deployment Request".

[Community Alums]

Hi @F_bio Santos ,

Please try the below code in the before business rule on an update of incident record:

In the script section of the Business Rule, use GlideRecord to check the parent incident's state and display an error if necessary.

(function executeRule(current, previous /*null when async*/) {
    // Check if the current incident has a parent
    if (current.parent) {
        var parent = new GlideRecord('incident');
        if (parent.get(current.parent)) {
            // Check parent incident's state
            if (parent.state == 6 /* Resolved */ || parent.state == 7 /* Closed */) {
                // Allow user to save the record
            } else {
                // Display error message
                gs.addErrorMessage('Parent ticket should be closed before closing child ticket');
                current.setAbortAction(true); // Prevent record from being saved
            }
        }
    }
})(current, previous);

If this helped you in any way, please hit the like button/mark it helpful. So it will help others to get the correct solution quickly.

Thanks,

Prasad.

[MGOPW]

Are you sure you're responding to the right question?

[Community Alums]

Sorry, my bad.

[Paige Duffey]

Hi, do you have the Pipeline setup correctly for each environment in the pipeline? I.E. all environments setup in your prod instance, with your prod environment marked as the controller and your controller environment setup in each instance in your pipeline? And lastly, that the credentials you are using for your pipeline have the appropriate permissions?

Here is a really good lab on nowlearning that can help you to ensure all of these items are setup properly: AEMC - Setup Pipeline

If all of that looks correct, I would start looking at the flows that are fired when the submit button is hit and see where the error is occurring from there.