Sometimes (I think that after creating pre-configured pages) SysWidgetDashboard_WidgetDashboardManager data packages appear in my repository. Do you know what are they used for?
No, there are no default widgets. Though, in case you previously had widget, but deleted it, or worked with section wizard clicking on the widgets, the system will have this kind of data in the package. It might not have data binded, but stays in case you will need it.
The web service will send a message to the page displayed in the iframe. The page should have it's own api to receive and process the request.
There is no way to pass a parameter into an iframe. There are just different pages and they can communicate in the ways how different websites are communicate.
This article might be of some help. Towards the bottom it outlines how to dynamically add an iframe on a tab and set the src of the iframe to a URL which includes a value from the record. You could use this same approach to create an iframe on the contact and set the src url including the contacts ID value.
Unfortunately, It's not possible to perform from JS. On the other hand, there is no point to do that. Business processes have their life cycle and when the edit page is open, the business process stays on hold. It will continue working after a user completes the edit page
1)Or enter the string resource on the page or enter directly (2nd option)
Localized strings and images are the resources of the client schema that are most often used in the implementation logic of the module.
Add resources to the client schema in the [Structure] tab of the client schema designer. The application core automatically generates a special [Client module name]Resources module, which contains resources of the client module. The localizableStrings property stores schema's localized strings. The images property stores image resources.
In order to access a resource module from a client module, you need to import the resource module as a dependency into the client module.
Please investigate how the "activeRowActionOpenCard" button was added into the "SupplyPaymentDetailV2" module. Please feel free to create your own container and apply your CSS in order to create the left button. The handler for the buttons is in the "onActiveRowAction" method in the "ConfigurationGridUtilities" module. Please put a breakpoint and click on the button on a record in the "Installment plan" detail on the "Order" page. You'll see how to handle the click. Please note that you can override the "onActiveRowAction" method on the detail schema.
Please read bpm'online development guide for more information.
When I create a process and a pre-configured page in this process I get two sets of language resources: one for the process and one for the page. Page resource files contain translatable strings for all the UI elements on that page. Process resource files contain translatable string for the process: things like parameter names, step names, etc.
I wanted to translate my pre-configured page, so I edited resource.pl-PL.xml and translated all the strings. It turned out it had no visible impact at all, the page was still entirely in English. Only when I translated process parameters connected to the page UI elements, the page got translated. Why is that so? What's the purpose of page translation files if they don't seem to have impact on the UI?
I do not understand about what resource.pl-PL.xml you are talking. Translations for business processes are located in Translations section. Could you add some screenshots to clarify your point?
The Translations section seems very unintuitive. There are a lot of strings there that I'm not interested in translating, cause they're not even visible to the user and I don't know how to find those that I'm interested in. I tend to write translations in translation files directly (like resource.pl-PL.xml). Those files get created along with their schmas - for example if I create a pre-configured page UsrCustomPage I get a schema in MyPackage/UsrCustomPage and translation files in MyPackage/UsrCustomPage.ClientUnit
You should read this topic with subtopics to find out how to use the Translations section. Just filter by the key contains [name of business process] and you will see all the data you need. After that open the first row in a separate window using special button, translate it and click Next to open the next string to translate. Then just click “Apply translations”.
Since you are using File design mode you could not apply translations when did a half of a translation job.
I'm sorry but it's not very helpful. First of all filtering, by "key contains [name of business process]" includes a lot of strings that don't need translation (process step names, flow names, process parameter names, etc.). But that's beside the point. What I meant in the original question is that the page translation strings seem to have no impact on anything. I'll give an example: I have a process step named PreconfiguredPageTranslationTask and it is connected to a page called UsrClientUnit1. I translated all the strings for the page UserClientUnit1:
It has no impact on the page:
I then translated a process parameter connected with PreconfiguredPageTranslationTask:
It has impact on the page:
So the effect is the same as when translating the resource files directly. Back to my original question - what's the purpose of the page translation strings if they don't seem to affect anything?
Ok, thank you very much for the explanation. To be honest it seems confusing, I wish there was a clearer separation between translation strings that the average user sees and the ones that appear in the designer and only developers see.
After refreshing page on my custom sections I get the following error:
GET http://localhost/0/QuickFilterViewV2Resources.js 404 (Not Found)
It does not happen on Contacts or Accounts sections and it doesn't happen if I just enter my sections normally (no refreshing). Do you know what I'm doing wrong that I get this error?
The issue happens due to the fact that the static content is disabled and the development in the file system option is enabled. At the moment the only way to bypass is to add the QuickFilterViewV2 module into the define of every schema of the sections where you face the issue.
Anyway, you can ignore the exception on development instances. It won't affect production ones.
Let's say I read one object using Read data step and I choose to only read columns First name and Last name. How do I reference that data in Script task? I know I can copy those strings from step parameters to process parameters using Formula step but maybe there is a better way.
For the [Script-task] elements and methods that have the [For an interpreted process] checkbox selected, the wrapper class is generated that contains the initialization and declaration of methods. This wrapper enables you to access the process values.
The Get method returns the value of an item or process.
Method signature:
Get<T>(string path)
where:
T — parameter value type.
path — a string that specifies the path to a parameter or property. The path is built according to these rules:
You don't need any parameters and select any specific columns to read in the element Read Data, simply use “element name.property name” to get the field value in the Script task.
As far as we can see from your method you are trying to read values from the "UsrFirstName" column and we don't know what data is stored there and what are you trying to read. Please re-check all your columns and also try Grigoriy's suggestion about filters.
Does anyone know if this is still the case? i.e. that it's necessary to save each individual field to a parameter in order to access them inside a Script Task element of a Business Process? It seems like it really should be simpler to access data on any of the fields!
I am aware of being able to query the entity directly within the Script Task, but I'd like to keep as much of the business logic in easy-to-read BP steps as possible, including reading data.
Yes, the logic remains the same. There is still to call for read data element through the script task without the intermediate process parameters or settings. This logic will be review by our developers, it is confirmed by our R&D but we do not know when it will be done.