search results

(...) ICacheStore cacheStore) w WebCon.WorkFlow.Studio.Logic.Managers.StepsManager.GetSteps(StepsCollection steps, Int32 workFlowID, ICacheStore cacheStore) w WebCon.WorkFlow.Studio.Logic.Managers.workflows Manager.FillWorkFlowEntity(Documentworkflows Collection collection, WorkFlow dalEntity, WFStepForm defaultForm, WFStepForm mobileForm, ICacheStore cacheStore, Dictionary`2 stats) w WebCon.WorkFlow. (...)

(...) FDefinitions as actionProcess on DEF_ID = ACT_DEFID join DicActionKinds on ACT_ActionKindID = DicActionKinds.TypeID join DicActionTypes on ACT_ActionTypeID = DicActionTypes.TypeID left join workflows on ACT_WFID = WF_ID left join WFSteps on ACT_STPID = STP_ID left join WFAvaiblePaths on ACT_PATHID = PATH_ID left join WFPlugIns on PLU_ID = ACT_PLUID left join Automations as actionDefin (...)

(...) CacheStore cacheStore) at WebCon.WorkFlow.Studio.Logic.Managers.StepsManager.GetSteps(StepsCollection steps, Int32 workFlowID, ICacheStore cacheStore) at WebCon.WorkFlow.Studio.Logic.Managers.workflows Manager.FillWorkFlowEntity(Documentworkflows Collection collection, WorkFlow dalEntity, WFStepForm defaultForm, WFStepForm mobileForm, ICacheStore cacheStore, Dictionary`2 stats) at WebCon.WorkFlow (...)

(...) in workflow (with a list of the workflow participants) and a sub-workflow for each participant. After the "Start" step, I want the attachment to be read-only. In both the main workflow and the sub-workflows , it should not be possible to add an attachment, nor remove an existing one. Are there any ideas here? Thanks Ernst

(...) s Access License. The users of the child workflow have a Single-Solution Access License. After the parent started a few child workflow and is in the "Waiting for sub workflow" step. Once the child workflows are completed the parent workflow should move on. This works fine, if the user completing the child workflow has an Unlimited-Solutions Access License. If the user has a Single-Solution Access Licen (...)

(...) the scope App.UserDefAPI.ReadWrite.All (according to documentation this is necessary to get access to endpoint with automation). In addition the REST API client is application admin, can start new workflows and so on... What I am trying to do is a POST to an automation endpoint, which starts another workflow in its automation (very simple). But all I am getting is, regardless of what I do: { (...)

(...) ws, where each row represents a new item, is it possible to allow them to start new instances of a given process based on that file? In this case, the goal would be to automatically create 100 new workflows .

(...) Hi everyone, I’m working on a feature, where single button triggers a set of actions that grants permissions across related parent and child workflows , and delegates active task to other user using REST API. I'm currently facing a frustrating issue with the task delegation API using the endpoint POST /api/data/v6.0/db/{dbId}/elements/{elementId}/admin/tasks/assignment When I use this endpoint via Swag (...)

(...) ations the Advanced Analytics Framework is very useful. Currently a user needs at least the role "Business Administrator". But we do not want to give this high-level access rights (change / delete workflows ) to our analysts (department manager, process manager, ....) So a dedicated Role "Analytics" (in combination with read all instances) would be very helpful. Currently, the only way to provide d (...)

(...) Hi, I'm writing this post to verify, that I didn't overlooked an option. Situation: I have a data table to get the data of subworkflows and the base 64 encoded values of their attached images. This data table is used to create a word document. The standard SQL connection uses the bps_user which neither can read data from a separate database nor is the user allowed to read the attachment file table: (...)

(...) Hi, when entering a workflow -> Main form -> Attachments section there is an option called 'Related attachments'. This is really useful since it allows displaying attachments from sub-workflows /parent workflows or via SQL and it can save a lot of disk space. The issue is that the related attachments don't appear in the same tab as standard attachments. Users, unless they are aware of the second tab, usual (...)