search results

(...) r invoking the “Stop sharing” action only ends the sharing, not the task itself. Information on all finished sharings is recorded by the service in a dedicated table containing sharing History – History SharedInstances. The same principle applies to the previously mentioned situations that involve changing the type of sharing. For example, transiting a path will replace the existing s (...)

(...) information about assigning a task to a group is presented in the form in the “Assigned to” field (the blue frame).   The information on task execution is also available in the History after clicking the History button (the clock icon above the user information panel) and then clicking the icon of a selected step. The screen tip displayed below the icon provides information on peop (...)

(...) t, you can filter looking for a range, or find those that Exceed/Fit in the expected time.   Last but certainly not least, configured performance indicators will appear in the Instance History . These will be shown differently depending on if the calculation is ongoing, was paused and restarted, or has finished. History showing time in one step: History showing ongoing indicator: (...)

(...) ndependent of the WEBCON BPS version, so a system update will not require any changes to the service. Any information on the possible need to update the service will be included in the relevant "History of changes" document.    

(...) arching through external personal databases (other than BPS process) WebCon.WorkFlow.Extensions.GDPR.Actions.FillPersonalDataItemListCustomData Action deleting attachments along with their History WebCon.WorkFlow.Extensions.GDPR.Actions.RemoveAttachmentWithHistory Action Action saving specified user IDs to a technical field WebCon.WorkFlow.Extensions.GDPR.Actions.SaveIdsToTechn (...)

(...) mobile application proper permissions to retrieve information about the device location; otherwise, they will not be able to complete it. The information about user location is saved in the instance History . It can be accessed only by individuals authorized to display the instance History in the admin mode (the gear icon). Once you click the path icon in the upper right corner of a newly opened window, (...)

(...) m the data source without applying additional uniqueness conditions. As a result, some of the rows are duplicated, as indicated in the figure above. Additionally, the log available in the instance History informs that 15 rows were added as a result of the action.   Clear item list This action removes all rows from the Item list specified in the configuration. The action also removes (...)

(...) ed” of to their own subworkflow instance, their participation can be limited to this instance only - they will not be able to peak at data from the parent workflow or go digging in its instance History . The community site has multiple articles on how to use subworkflows in practical scenarios.   Assigning privileges and licenses Although licenses can be assigned manually through De (...)

(...) dquo; status in the CMD console. Additionally, the application logs can be accessed in a .txt file.   Fig. 5. Information on successful application  import in the CMD Import History Apart from being able to use the new/updated application on the target environment, users can now additionally check the details of an automated import that has been performed. As with the standar (...)

(...) . Depending on the setup you may have the same processes in multiple databases but these have different configuration. Business entities, connections, global costants etc.. We have a version History for the import in the system and not somewhere else, so we know who did it when with which configuration file.  We can keep track of all the imports. Some elements are always overwritten as (...)

(...) option will complete all tasks associated with an instance at a given step and enable path transition. Additionally, when an administrator completes a task, this action is documented in the instance History with the note “(Updated in administration mode)” in the Comments section.   Completion of a task by an administrator is documented in the instance History .   NOT (...)

(...) is used in a forbidden place will result in an error. The same is true for attempts to place such a field in a tab or group with access authorization, this will also result in an error.   History and admin mode Fields with access authorization are not included in the instance History . They are shown neither in the regular or admin mode. The only way to see historical data in these fields i (...)

(...) ended wherever there is a need for cyclical execution of the action that cannot be triggered globally in a standard way. The archiving of the technical workflow instance can be delayed so that the History (logs) can be accessed if the action fails.   Extensibility (+ example of sending to Azure Blob Storage) The are many applications of PowerShell in WEBCON BPS, including cyclical export (...)

(...) world case it would mean to deploy the process to production, invoke the new path for every instance and delete it afterwards, if possible. I'm not sure whether this is even possible, because of the History entries. Luckily this is only in the dev environment so it's not a real problem but even so this is something for which I would like to have a solution just in case.:) I wish everyone a pleasant w (...)

(...) We recently had a presentation of WEBCON BPS for a new customer. They came up with the question if not only changes of an element are being kept in History , but also views. So we need to define the definition, what as to be considered as a view. Sometimes you can tell a lot from what you see on a report already, but keeping track of this would be too much in my opinion. The easiest and most pragmatic (...)

(...) a dirty way by using an SQL Update directly on the WFElements table, but I am struggling by running this query by (cyclic) action on a separate path. The path is walking through fine according to the History , but no changes in the end. If I run the query with the "Test" functionality in the webcon Designer everything works fine. Do you have any idea, what is wrong or even better an other solution how I (...)

(...) Hello, I have a problem while adding a barcode. The instance is moving to the next step but the action is not executing, does not show any error and is not even logged in the History and is not adding a barcode. Does anyone had this problem on the latest version( 2021.1.3.163 ) , some thoughts ?

(...) Update WFElements set WFD_AttText1Glob = WFD_AttText1 where WFD_DTYPEID in ( select DTYPE_ID from WFDocTypes where DTYPE_Guid in ('31d8115c-a51a-451c-bdfd-ee17de78ab8c') ) Update WFHistory Elements set WFH_AttText1Glob = WFH_AttText1 where WFH_DTYPEID in ( select DTYPE_ID from WFDocTypes where DTYPE_Guid in ('31d8115c-a51a-451c-bdfd-ee17de78ab8c') ) Remarks: This is (...)

(...) Hello, Question 1: Is there any possibility to give user access to form but restrict/limit form History (only user have access to current form not for previous versions)? Question 2: I have form field 'Picture' in dictionary form which (that form) is connected with user by field 'User' - do you have any idea how to present that picture on users dashboard? Do be clear: Form 1: Field User: X (...)

(...) us scenario, when I look up an archived instance, I am able to bring up the form and see the files attached. However when I try to open/download the attachment it throws errors. Curiously if I go the History of the instance and scroll down to the attachment link, it opens the file just fine. Is this a known issue? Error during saga execution: Unexpected token 'A', "Attachment"... is not valid JSON Sy (...)