Q: Is there a way to change the color of the number in the featured metric
A: Not in 6.6, but that is currently in scope for the Fall release this year.
Q: For Featured Metrics, Is there any ability to add a Title that can be centered, rather than just the iView name?
A: Not at the moment. We will look at this as an enhancement.
Q: Are there any new formatting options available for bar or pie charts?Also, are there any plans to allow for maual ordering of columns in a bar chart?
A: We introduced some changes to the chart colors and changed some of the default options for new charts in version 6.5. That is still the latest. As regards ordering columns it follows the ordering of values in the list that was used to create the bar chart.
Q: Is bing license different from going to map from an address as we can do now?
A: Yes, it is a license for their Bing Maps API, which is different than the mapping you can use for free for daily use.
Q: Is the Map Type report available for SaaS?
Q: The API we acquire from Bing Map has any expirations? Is it licensed?
A: Those terms are all done directly with Bing. All Archer needs is the API Key, the terms/cost/times associated with are between your company and Bing.
Q: We are a Saas customer. Is geo maps available to us?
A: Absolutely is!
Q: Just an enhancement, if it has an expiration, ACPL can show that exp date
A: Thanks for the feedback. We actually looked at this during development and couldn't find an API call that returned the expiration date so we can't display it.
Q: For the email approval function, since every user needs to have that ability enabled, need the ability to have it as a default in Security Parameters.
A: Thank you for the feedback, Scott. We will look at this an enhancement.
Q: We always require comments when approving or rejecting. Does it mean we cannot use email approvals? Or is it possible to include comments into the email?
A: Not at the moment. This feature works for simple actions, that is actions that do not need any additional manual input.
Q: Wouldn’t the server info be the same for workflow as it would be for general notifications (in most cases)? Not understanding why it would be different. Further not understanding why a username/pwd is required.
A: In the event they are different we can capture the details. The user name and password is of a specific email account that Archer can monitor to process any emails received to complete AWF actions.
Q: Will advance workflow actions by email be made available to SaaS customers in the future? if so when?
A: Yes, this will made available in the forthcoming releases, please watch out for additional details on our monthly roadmap presentations￼.
Q: Is there a way to bulk enroll users?
A: Yes, there are options to enroll using APIs.
Q: Can you configure it for an entire group or does it have to be user by user?
A: At the moment it is user by user. The focus was towards executives, so this was designed as a fall back to ensure that only admin enabled users can work with this feature. This is a good idea though, we can look at this as an enhancement.
Q: Do you have to enable this feature (Advanced Workflow Approve by Email) for each user?
A: At this time, yes.
Q: When I send the email template generated from hitting the email action button nothing happens after waiting the allotted time set in the acp. What could be the cause of this?
A: It is difficult to answer without a lot of context, on a high level please make sure that the job engine is able to connect to the dedicated mailbox that has been set-up in ACP.
Q: Is there an API update to manage users to enable AWF Actions by Email programmatically or will we have to manually update each account?
A: The existing APIs (for user) can be used to programmatically update all users to be enabled for using this feature.
Q: I know that when an email is triggered from advanced workflow, it goes with a signature or a key and it validates that with response key to perform the action. How long the key will be valid?
A: There is no specific validity that has been programmed, users can use this feature if the original record is not changed in the meantime.
Q: what service governs the polling of emails for workflow? (AWF, job engine, other?) will discontinue job engine stop this?
A: It's a job that runs in the job engine up to every 15 minutes. The rate is configurable in the ACP.
Q: Are there any issues with setting up with authenticated SMTP? Our org is enforcing auth smtp and we found out OnDemand custom templates do not work with that. Does this feature have any such restrictions?
A: This feature uses existing On-Demand notification templates, with a new configuration that allows embedding Advanced Workflow buttons in the body of the email. The behavior should be similar.
Q: This is similar to mail monitor feed watching folder for emails to process?
A: Yes, it is a similar functionality.
Q: Question re user accounts: Did you add a upload user accounts functionality in Archer 6.6? We always have to manually configure users, and it can be very time consuming, especially, if we need to recreate all the test user accounts after environment ref.
A: The functionality to add users in RSA Archer is not part of the RSA Archer platform however, we have this utility: https://community.rsa.com/docs/DOC-94222
Q: Can I include attachments in the emails?
A: Yes, for the emails sent by RSA Archer to your users. The functionality of On-demand templates includes all existing functionality and adds the AWF buttons on the body of the email.
Q: What service governs the polling of emails for workflow? (AWF, job engine, other?) will discontinue job engine stop this? Can we stop updates during deployments...etc.
A: This is processed by the Job Engine. Yes, it can be discontinued as needed.
Q: In the example, what happens if the receiver chooses the button Re-Assign?
A: In your scenario, the re-assign button will work on the Archer Web UI but when the buttons are sent out they will be grayed out as this does not remain a simple action anymore.
Q: Can you elaborate on that token in the subject line? Is that the user's session token or some new token? Will that token expire if there are days between the initial email sent and the user approving a record?
A: It is a new token that has been created with this feature and includes a few details such as the username, email address, application id among other things. We have not set a limit for this token to expire.
Q: In the email notification example, when the user clicks on "approve" and the email opens up, if they type anything in the body of the email, would those comments be placed anywhere in Archer?
A: No. That information will not be transferred back to Archer.
Q: Can forwarded emails be approved by other individuals who are not the required approvers?
Q: The token is attached to the email address?
A: Yes. It is encoded in the email. The user cannot see the token.
Q: The buttons in the notification body can be placed anywhere within the body? Can that be customized? Or it will be at the bottom?
A: It will always be at the bottom. They are generated dynamically.
Q: is there plans to include this feature in the Generate Notification action via DDEs?
A: No, not at this time.
Q: I didn’t see a link to the record in the AWF email. Can this be added if they want to open the record up to review?
A: Yes, it depends on the content of your notification.
Q: Can we place the Distributed email address for email approval?
Q: Can the email be encrypted? What would stop someone from intercepting the email and responding on someone's behalf?
A: We recommend using this feature on a https:// network. This feature works by verifying the token that was sent out with the original email and the sender’s email id. This feature only works for users who are enabled to work on it, by default none of the users are enabled for this feature.
Q: Is there a time period where the approver could theoretically wait too long to respond?
A: As long as the record is in the same state, the email should work.
Q: Can email be sent to group of users and can anyone from the group be able to approve the record?
Q: Why can't this be used for DL's? How different is that from normal user email addresses?
A: A DL isn't a user, it's an email sent to a group of users. Since the token is tied to the email, the response would have to come from the DL not an individual member of it.
Q: What happens if a user approves via email and before its updates the records user again approved directly in Archer
A: In your scenario, the user will get an error notification stating that the action could not be completed via email. This will happen because the record is already approved in the system by the time email is received.
Q: My guess is that the distribution list will not work as the reply would have to come from the dist list address
A: That's our thinking too.
Q: What about if an "approver" changes/get reassigned? How is that handled?
A: The original user will get an error email, if they try to process it.
Q: When the Send email pops up with the key in the subject, is the subject non-editable to the user?
A: Users should not edit the subject, but it is not locked down from being able to do so. Editing it will cause failure.
Q: Can notifications be sent to many users and anyone can approve like we have in ServiceNow? This is much needed.
A: It is a configuration within the workflow.
Q: How does the "reassign" button work in the email?
A: It depends on how the workflow has been configured.
Q: Will this integrate with Archer's digital signature feature in the future?
A: Most likely not. We are also working on a mobile application, which should better serve this need.
Q: Is the token via email one-time use?
A: Yes. It is.
Q: Was the API updated to manage users to enable AWF Actions by Email programmatically or will we have to manually update each account?
Q: When a "approver" is changed, does a new email go out or does the approval have to happen in the system?
A: This again depends on how the workflow was configured in your Archer instance. If there is notification that goes out at the relevant node where changes are made, email will go out again.
Q: The ACPL configuration for email: Is that for a single mailbox? Many users would have rules to push them to different folders. How are they monitored?
A: No, this is a new email that needs to be configured, so that Archer can monitor any emails coming to it using this feature. It is not user specific.
Q: What happens if you assign or reassign a record to a user who doesn't have Approve by Email enabled, but that's what was configured in the AWF?
A: In your scenario, the user will not receive any email from this feature.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.