Jon,
I have created a POC workflow to support limiting the maximum number of rows in an export. It is a workflow that accepts either a set of selected records (which will likely mean the # selected doesn't exceed the maximum) or a selected saved set. If either exceeds the maximum defined in the Configuration repository, it arbitrarily limits it to the specified maximum (vs. rejecting the export). This workflow uses the Callout BICs: Set Properties BIC, SQL Create Saved Set BIC, SQL Set Properties BIC, and Initiate Scheduled Export BIC. In order to send a Saved Set to the workflow, the <repository> -> Edit -> Workflow Properties settings need to be configured to point to the starting point activity in this workflow, which means it's the only workflow that can process saved sets. If you DID have more than one workflow that needed saved sets, then a master workflow would need to be implemented in which the desired workflow (or subflow) was invoked base don user selection in the submission form.
I have uploaded an export of the workflow. The submission form (Work Item Type) it uses is a basic one that only provides a comment field so it was not included in the file.
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 9099009179
------------------------------
Original Message:
Sent: 12-19-2020 11:53
From: Jonathan Varo
Subject: Possible To Limit Export of Records
Hi Brian,
I would definitely be interested in the Point of Concept example.
Thanks!
------------------------------
Jonathan Varo | PIM Lead
Fender Musical Instruments | 480-845-5823
Original Message:
Sent: 12-06-2020 23:46
From: Brian Zupke
Subject: Possible To Limit Export of Records
Jonathan,
One option to limiting the maximum records for a group of users would be to disable the ability to invoke direct exports, but instead initiate a workflow on the selected records (or saved set) and then having that workflow clip the number of records to be included to some configurable maximum. A POC for this approach was implemented as a workaround to this very issue and can be demonstrated with little effort if interested. The key limitations are the group of users to be affected would only be able to launch exports for those repositories connected to this workflow and the export(s) would be constrained by pre-defined exports (vs. current view which allows any attributes per export).
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 9099009179
Original Message:
Sent: 10-21-2020 09:55
From: Jonathan Varo
Subject: Possible To Limit Export of Records
Recently, we've had an issue where somebody used the Select All button in Enable 8.2 and proceeded to download every image that they had access to. Because the system allowed this, the resulting file was so large that it crashed the system. Is there a limit that you can set to avoid these issues. The Select All button in gallery view makes this a little too easy to do; especially for new users.
Thanks,
------------------------------
Jonathan Varo | PIM Lead
Fender Musical Instruments | 480-845-5823
------------------------------