Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

john-baldwinNew Participant

Improvements to Document Custom IntegrationsNew

The Workfront experience for Document->Custom Integrations lacks several critical pieces of functionality that have resulted in extended downtime on our systems. For example, we have had instances where the Adobe Enhanced Connector will stop processing project properly. However there is no indication in Workfront that there is any problem. In the case of a failure is with the Workfront functionality, Workfront will stop sending data to the connector if it detects too many failures when sending data. Although detecting failures and halting communication to avoid complication has merit, the implementation within Workfront is deeply flawed. The communication from Workfront to the Enhanced Connector happens through the Custom Integration system in Workfront (Setup -> Documents -> Custom Integration).The Custom Integration Feature uses an API key that must match between AEM and Workfront. Generally, this works acceptably.The Custom Integration Feature, however, is flawed in significant ways:There is no way to remove old integrations. We have 27 integration configurations in the system, but only 4 are needed.When a custom integration is marked “frozen” or “disabled” in Workfront, there is no indication in the UI.When a custom integration is marked “frozen” or “disabled” there is no notification to alert admins.There is no UI to un-freeze or re-enable a custom integration.There are no logs that we can view that show the state of the custom integration.The authorization token for the interface is not visible, but if it is not the same between systems, the interface will fail.Multiple custom integrations can share the same name and same destination. This can (and has) resulted in confusion regarding which custom integration should be made active.If a new integration is set up, its auth token will be different, and existing project communications will fail. Recently, we had to revert the auth token value to a previous state using methods described below.There is an API call we can use to access the event subscriptions, which are the message identifiers for current integrations:The API results do not show the name of the integration. Only the GUID is shown for the specific event subscription in the API. The GUID is not visible in the UI, so alignment is difficult.The API returns 160,383 results currently, so it can be a fishing expedition to locate the relevant records to determine current state.Even if we locate the record that tells us whether the custom integration is frozen or disabled, we cannot fix the state with this API. It has some benefit for identification.The authorization token is visible in the API results, but to verify it against AEM requires hashing the token (using asystem/console/crypto interface in AEM) to compare to the existing configuration. In addition to not being visible, most of this is not documented and requires getting to the Workfront engineering team to restore our connection communication to resolve the issue. We cannot simply create a new connection, because a new connection would disable all existing communication between the systems and would break all existing projects. So we need to restore the existing connection. Because of the above complications, when we encounter a connector issue, we face hours, and sometimes days, of downtime while we explain to initial support team the issue. We need to repeatedly escalate to resolve. What would we like changed: We would like to be able to remove outdated custom integrations.We would like to be able to see the current status of any custom integration.We would like to ability to unfreeze and re-enable any custom integration.We would like a UI to allow us to match the auth token between the two systems. This ideally would happen automatically.We would like to be able to review logs to understand the current state of the integration without requiring assistance from Adobe.We would like the custom integration process to be documented to ensure both ourselves and Adobe support understand and can resolve the problem quickly.

GrahamJarrett
GrahamJarrettNew Participant

Board Columns to allow addition of Custom Forms / Auto Add a custom form if moved into a columnNew

Description - Similar to allowing the addition of Tags or changing the Assignee, Board columns should allow the affition of or the auto addition of named Custom FormsWhy is this feature important to you - Data is often only required at stages as the item travels through the stages of a project and is often NOT required to be entered at the initiation of the item, additional information may be required to be added by a specific person. By facilitating the addition of a board combined with the assignment of the card to a person or team, the data will be entered at just the right point in timeHow would you like the feature to work - Add an additional option on the Column Edit under the Update Field Values Automatically, add an option for the user to select a custom form or in the board definition set the form(s) to be added. Could also do this in the same way as defining Members for a Board so that only a limited number of forms can be displayed on a particular Board. Bonus, it would be awesome if values in the form could be set based on being moved into this column. When setting up the custom form on the column you would need to have a switch next to each field to allow the value to either be maintained or to be set (similar to the switches for Project Preferences). If "Enabled" for a field, then the board would allow a value to be set. Bonus Bonus to this, is that the "Overview" or "Financial" fields should be able to be included as if they were custom forms with the same enablement. Bonus, Bonus, Bonus... Allow Project Level Forms to be included based on security, with the same "Enabled" switch on fields.Current Behaviour - Cannot add Forms

IM1New Participant

BoardsNew

Allow "backwards integration" back into a Workfront project.  I created a standalone board, but it lacked the full set of features available in project-based boards (more on those features below).  I had to manually connect each card into the project.  Also, each new card that is created cannot be connected, so I will need to manually connect new cards created by the team (if you use the "Create connected card" feature it only lets you pick from tasks in the project, but doesn't let you create an entirely new task)Allow document upload in standalone BoardsDon't let team members delete standalone BoardsEnable the Tags feature in project-based BoardsMake it easier to change the column names in project-based BoardsAdd an option that defaults each new card in standalone Boards to be connected to a projectAdd a "general information" section to standalone boards so that you can leave general information for the team (i.e. project description, general rules for using the board, links to folder locations, etc.)Allow filters for custom card fields (i.e. Priority)Enable reporting or at least export of data for standalone BoardsWhen you Group cards, it creates a redundant scroll bar that takes up spaceAllow the owner of standalone Boards to change the Status options (the seem to default to System Defaults)The standalone Boards load faster and have a better GUI than the project-based Boards, which seem to be buggy and load slowlyEnable notifications to be customized for standalone Boards