January
Welcome to the January 2024! ✨ release of KuFlow.
We start a new year at KuFlow providing new features to our users:
Defining and using custom user data 🎎
During the creation of your workflows, you have probably on more than one occasion needed to be able to obtain specific information from a given user in order to make decisions. Usually accessing this information is not a problem if you use your own workers since they are deployed in the client's network and therefore have access to corporate services and databases. However, on other occasions it may be the case that you do not have a database with information about your users available in your corporate infrastructure, that it is insufficient or that you are simply developing a serverless process instead of a process managed by a worker.
For these cases, the organization's administrative users can define the scheme of a KuFlow form (in the same way as this type of form is defined for KuFlow tasks), which will be available to be completed for each of the organization's users. The completion of this form can be carried out by the administrator users of the organization or it is the user himself the one in charge of filling in his own form. With this functionality we have a specific bag of information for each user and its structure, or what information is requested, can be dynamically edited by each organization.
Custom data definition
The definition of the structure of customized user data is done in the "Organization" section of the administrative part of our application. Here you can define the structure of the data collection form.
Custom data completion
To fill in the information, you can do it in two ways. If you are an administrator user of the organization, you can fill in the information for each user from the "Users" section of the application. On the other hand, the rest of the users can only fill in their own information and to do so they can access the form by clicking on their name and accessing their profile (orange part of the application).
Access to information
The information contained in each user is accessible through our APIs. See the definition of our API Rest or the documentation of our SDKs. Similarly, in serverless processes, the information of the user task owner and process initiator is dynamically exposed in the serverless model so that it can be used in its definition.
SDKs updated 💝
We have updated all our SDKs to support the new features introduced as well as to introduce small improvements. We recommend that you update your Worker when possible. All changes introduced are backwards compatible with previous versions of the SDKs. Remember that we follow a semantic versioning of our libraries to help you in your updates.
