Product ideas | Community
Skip to main content

10000 Ideas

Jennifer_Dungan
Jennifer_DunganNew Participant

Data Warehouse Account and Location ManagementNew

Description The new Data Warehouse experience allows us to save re-usable accounts and locations, this is nice rather than having to manually add where to send our files and re-enter all the authentication, etc... but there is a huge oversight here.... there is no way to delete or edit those items once added (as far as I can tell anyway).   Old emails, migrated FTP servers, changes to cloud servers where files need to be sent will need to be updated... We don't want irrelevant items to be clogging up the selection screen... even "one time emails" need to be saved as an Account and a Location, but we may not want that to stay in the system as a permanent option...    Why is this feature important to you We need to be able to keep our systems clean so that reports don't fail due to using old, irrelevant locations... particularly if names are like "Company FTP"... what happens when that moves, "Company FTP New"? "Company FTP New 2"... not being able to remove and clean up the accounts is ridiculous... this should be a standard feature without needing to request it.     How would you like the feature to work I think there should be multiple places to access... first, there should be an "edit" button within the Data Warehouse UI for the account / location selected (so it can be reviewed and edited right there, with the option to delete if needed). However, there should also be an area in the Admin area that allows us to manage items in bulk (like for when doing a yearly cleanup).     Current Behaviour This is non-existent currently... we can add but not review the details, edit, or delete.

ThoreEhrichNew Participant

Resource Management Home Office ExtensionNew

Description - After the Corona Home Office, a lot of people are still working part time in the Home Office. It would be a great extension of the Resource Management, when the user are able to set in Workfront if they are in the Office or in the Home Office and that even for the future weeks. For example the users are able to set from where they are working in the next four (4) weeks. So that in the end we can report on the entries and the users get an overview which of the colleagues are in the office or not. Why is this feature important to you - To get a better visibility in the planning of projects it would help to know upfront if the colleagues are in the office or in Home Office. How would you like the feature to work - It would be the best when we can include such a functionality in the timesheets. Because every user is using the timesheets and knows how to work with it. The difference to the other entries is that there is not impact on the hours in the timesheet. The user only enters for a day Home Office or Office and then to the Tasks, Projects, etc. the actual worked hours. Current Behaviour - We have created a project where we enter the users at each day with a Custom Field where each user can set if he is in the Office or in the Home Office. To have a better visualization we created a report and dashboard for it. So that we are able to pin it to the upper Navigation.

bjoern__koth
bjoern__kothNew Participant

Initializing a Web SDK "Data Variable" Data Element type, similar to "XDM object"New

Description -  I LOVE (yes, that's uppercase!) the Web SDK "Data Variable" Data Element Type in conjunction with the "Update variable" action. Especially with the new UI, it looks almost exactly like AppMeasurement, even better. What I am missing is a way to initialize the DE in a similar way an "XDM object" can be defined directly in the Data Element section, to set an initial state, and which you can build upon in your rules to temporarily enhance it. After the rules have completed, the initial state is reset. In my current setup with the ACDL (Adobe Client Data Layer), I need a standalone rule that is listening to "all events" and runs before any other ACDL triggered rule that further updates the variable, just to achieve this functionality. Or am I missing a step / functionality? As a workaround, I could likely also create a "custom code" DE instead, that defines the core data structure as JS object, and can then be merged with the variable part and the result used instead. This would remove the need for an additional rule, but would also require you to be savvy enough to write that code yourself. Why is this feature important to you? - It creates the need for unnecessary workarounds to set the globally applied pieces on the DE. How would you like the feature to work? - The XDM object can also be defined in the Data Elements section, why not the variable data element as well?In the DE definition, why not already display the same UI that is presented in the update variable step?  Current Behaviour - Cumbersome additional step/rule needed to set commonly used parts on the data element e.g., through a custom rule that runs before the actual page view or interaction rule