I have created custom workflow for reviewing the content before publishing if the content is okay admin will approve if it needs any changes admin will reject the content. in both cases workflow send email to the initiator?
by default its taking input template from /etc/workflow/notification/email/default/en.txt
when i made changes to this file its not reflecting in that workflow email notification to the user. I want to customize the template. Is there anyway to overcome this problem?
Restarting com.day.cq.mailer.DefaultMailService on 6.3 solved the same issue for me. Restarting the whole AEM also worked, btw.
Related
I set up new automation.
Created email templates with personalized tokens, added these tokens in my CSV file.
Uploaded CVS contacts with personalization tokens (created new separate contact list).
Connected uploaded contact list to new automation.
Set up automation "LIVE".
RESULT: system assigned new contacts/emails to the old templates/automation which I didn't have intent to use.
Also was weird, in old templates/automation were similar tokens {firs name}, {company} {line} but they weren't applied, only DEFAUL appeared instead of these tokens. Could you please help me understand how did it happen and avoid it in the future.
My goal is to use SendGrid in cold email outreach where I am going to create 2-3 new automations per week. I am using plain text in builder. Can you please show me the way to do it without mess I described above.
When I send emails using SendGrid automation these emails doesn't appear in my Inbox "Sent" folder.
Can you also help me to fix that
I don't what I need to try to fix that
I set up a DevOps post-deployment approval system successfully. When the user gets a mail to approve my changes in my project, the summary looks like this:
Summary screenshot
Is there a way to show the commits I made which are getting installed in this version. The idea is to make it easier for the customer to get the newest changes out of this mail.
Thank you in advance!
Is there a way to show the commits I made which are getting installed
in this version.
For this issue , if your release pipeline uses build as the artifact source, then the build version will be displayed in the pending approval email. Clicking build version will jump to the corresponding build page. In this build summary page, you will see the corresponding commits. Then click on this commit to view detailed changes.
If you want to display detailed commit information in the email summary, I am afraid this is currently not supported. The content that can be displayed in the notifications email is designed and cannot be changed. You could add your request for this feature on our UserVoice site , which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps.
I created a Custom workflow added a participant step to user review. Since few days back i am not able to see the participant step Notification in AEM Inbox :(
I checked Permission and everything its works fine, I am using AEM 6.2
My Workflow model:- /etc/workflow/models/HPE_Review.html
The same way my current Running Workflow Instance Also not showing.
Can anybody help me to enable Inbox notification?
I need a setup where users can update a page and then submit it for approval/activation in AEM 6.2. The page would be submitted to workflow where a content approver/administrator would review and publish the page. This seems like a common setup for content managment, but I can't figure out how to do it in AEM.
I have done the following:
setup a user that has permission to update but does NOT have
replicate permission on folderX.
setup users with update and replicate permissions on folderX and added them to a group "content-authors-approvers"
created a workflow where the first step of the workflow is the page will be submitted for approval and publication to member of "content-authors-approvers" group
assigned this workflow to folderX
However, when a user does NOT have replicate permission, the "publish" option does not show up at all. This makes sense, really....but then, how does one go about setting up a workflow like this?
From what I've read about this in earlier versions of AEM/CQ5, the replicate/publish option was still available to all users, but it would automatically kick off workflow if the user did not have replicate permissions. (see Start a workflow on page activation without activating the page in CQ5 )
this seems to have changed in 6.2. can anyone help?
I have tried looking up online, but found nothing
There is a native workflow to handle that. It's named Publish Example. see it here: http://localhost:4502/etc/workflow/models/publish_example.html . I believe that it's better then the automatic triggering cause the author actually knows he triggers a workflow (whilst when it happened automatically there was no info about that). To explicitly call it you have to either from /siteadmin select a page and click workflow on it, or do it from sidekick or in touch.
sidekick:
touch - editpage:
I've been looking for a few days now for a way to disable the automatic customer registration that occurs when a customer finishes an order in the checkout in Magento. What happens is that the user is logged in to his or her account, and two emails are sent. One containing the order confirmation, and another one, welcoming the user as a customer, including his or her account information.
What I'd like to do is to disable the email containing the welcome, and disable the registration/ login of the account.
Like I said, I've been trying to find some leads on where to look for a few days now, but to no avail. I'd appreciate if someone could help me figure out what files to look at, and also what parts of those files.
Also, maybe I should mention that the website is using a One Step Checkout.
Thanks in advance,
Base on your system setting you need to make changes in one of the two files listed below. Copy the templates to your custom theme folder and make the changes as needed to remove the login section and links.
/app/design/frontend/base/default/template/checkout/onepage/login.phtml
/app/design/frontend/base/default/template/persistent/checkout/onepage/login.phtml