nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Alert for deployed files

krithick

I have a list of files, which when deployed should send a email alert to my team. Has anyone tried this using Open Deploy.

Find more posts tagged with

Comments

Bhargav Coca

it can easily be done in the workflow as a success email. Instead of sending to the Content Author (The Person who Initialized the workflow). Youw ould send it to the whole group to whom you want to send the success email that thier deployments are good in Prod.

IS this what you are asking?

Adam Stoller

I have a list of files, which when deployed should send a email alert to my team. Has anyone tried this using Open Deploy.

Besides lillywhite's recommendation - if you really want to do this via OpenDeploy - you could either add a dnrDeployment script to your deployment configurations (where the script could parse the list of deployed files and compare it against a known list of files for which email should be sent - and then send the email if there is a match) or try to move the matching logic into the deployment configuration file using one or more dnrFile directives.
I think handling it from the workflow end is generally best, a dnrDeployment script second best, and dnrFile directives the least recommended of the three options.

claudiag

I've never done this using strictly OD - it's always been part of either a WFT or a WFM. If you're using a workflow at all, this is simplicity itself.

If you're not using a workflow, a deploy and run is your only option. It's more of a headache, but doable.

Adam Stoller

If I understand the issue correctly (which is certainly questionable) - there is a list of N files for which they want special notification - and any of these N files (0 to N) may be attached to a workflow and thus may be deployed.

The "normal" email notification regarding files attached the job would probably still go out - but they want "special" email notification if any of these N files get deployed.

Based on that understanding - the DNR is probably a reasonable solution, though a custom External Task could also be used. In either case, one would have to compare the list of files being processed against the list of N files for which special notification is required and then "do the right thing".

If I misunderstood the issue and they want notification for all files that get deployed - then the External Task via the workflow is almost always the better choice.

Two Crosstabs Into Another Crosstab.rptdesign

claudiag

If I understand the issue correctly (which is certainly questionable) - there is a list of N files for which they want special notification - and any of these N files (0 to N) may be attached to a workflow and thus may be deployed.

The "normal" email notification regarding files attached the job would probably still go out - but they want "special" email notification if any of these N files get deployed.

Based on that understanding - the DNR is probably a reasonable solution, though a custom External Task could also be used. In either case, one would have to compare the list of files being processed against the list of N files for which special notification is required and then "do the right thing".

If I misunderstood the issue and they want notification for all files that get deployed - then the External Task via the workflow is almost always the better choice.

Re-reading the above, I think you're right. Being that's the case, External Task vs DNR is really six of one, half a dozen of the other.

The lazy way to do this is probably to have those files in a separate branch (if you're able) and have a different WF/OD for them, so you don't have to maintain a file list to compare, but that might not be feasible based on the set up.