Hi Jakub,The short answer is, no, you cannot change the edit mode in client configurations.The editable property that Alexander has displayed controls if a field is editable or not. I think what you are inquiring about is if it is possible to change the edit mode. In IFS Cloud, you will see "Single Cell Edit," "Single Row Edit," and "Multi Row Edit." For single cell and single row edit modes, the user can place the cursor into a field and start editing. For these modes, the save is also automatic when you leave the cell or row. Multi-row edit is where you have to manually start and end a save transaction.The different save modes are used depending on what is suitable for the expected user behavior and, of course, how the data entity is structured. I can see that not all users would agree on how "suitable" the chosen save mode is for every context. However, one must keep in mind that these modes are, by technical reasons, not directly interchangeable. There is also more to it than just
Hi Dan, Unfortunately, the type of date-time support functions you are asking for is currently not supported in the client (layout attribute conditions). We are discussing extending this functionality within current development, but for now, you are restricted to static value comparisons. Kind regardsTobias
Hi, The conditions on layout attributes are client only. I think that you may have been lead to believe that “api” functions could call server api’s which is not the case. “api” prefix just instruct the condition parser that this is a helper function. The available functions for the condition syntax are the ones that are listed in the technical documentation. Currently there is no support for user in the conditions. You can access the client context values but user is not part of that set. context.Company = “01” I don’t know for what scenario you would like to address the current user. For a scenario where a specific user or user group should not have some fields visible. It would be possible to hide these fields in a custom context configuration and then map that context to the specific user / user group. Kind regardsTobias
@ThejanJay as you have already found. This is a limitation that is there because of a technical limitation in our design. I won’t try to explain this in detail. But it has to do with the key custom attribute references are using (objkey) and that key is not part of the main key in the odata provider. Main point is that this is not something that we could change with a small correction but would require a more extensive development project. kind regards,/Tobias
Hi Fabrice,It should be possible to escape the quote and and the condition validator is written to handle this in a variety of ways. x = ‘ “ ‘ | “ \” “ | “ ‘ “ | ‘ \’ ‘ However, looking into you scenario we have found that this is not working as intended in combination with the expression evaluator. An oversight from our end, and we are now looking into a solution for this. Kind regards,Tobias
Yes, support for one-to-one associations have been added. Please see user documentation at https://docs.ifs.com/techdocs/23r2/040_tailoring/225_configuration/200_client_configurations/250_entity_configurations/master_detail_relationships/#one-to-one_detail_view
Hi,When you click "New" on a Command group/Content collection, you will be prompted to insert some "specific types" of commands, as well as references to existing commands. This is analogous to adding an element to a page/content collection. For example, when you add a group, a dialog opens where you select the group to add. What you have added to the page content is actually a reference element that points to a group. The page itself does not hold the group.CommandRef is a reference to a command. You use this if there is already a command that you want to enable on the command group.Note: the command picker will not assist you in displaying only valid commands for the context. As a developer, you need to be aware that the referenced command is applicable to the context you are adding it https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/200_client_configurations/100_page_designer_basics/#change_active_page
Hi,@Priyanka Cecilia V as I undestand it, the problem that you have with custom attributes is that you do not prefix them with a namespace, e.g., record, parent. See if your issue is solved by using the record namespace.record.cf_Name != nullConditional Fields:https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/200_client_configurations/310_conditional_fields/ Condition Syntax:https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/200_client_configurations/310_conditional_fields/300_condition_syntax/
Hi, This is a feature limitation in framework tracks prior to 23.New projection - extends standard projection does not support object connections. A custom projection for a custom entity do support object connections.From 23R1 both scenarios will support object connections. RegardsTobias
As far as I know the UI element that you ask to configure is not part of the Client Layout Metadata, i.e., not described in the metadata but statically generated by the calendar control. That means that you will not be able to configure this aspect of the calendar. Kind regardsTobias
Hi Rakesh, Sorry for a very late answer. But here is for what it’s worth. Assuming that you want to connect TrackingInformation against the Purchase Order Lines Part list records. The association is made between the custom TrackingInformation and CustomerOrderLines entity is then wrong. The Purchase Order Lines Part list is of PurchaseOrderLinesPart entity, and you should create an association between those two. You can control this by inspecting the metadata returned to the client when navigating to the page, using the chrome explorer. Projection/Entities/PurchaseOrderLinePart/Arrays. If your association is created correctly there should be a TrackAssoc in the arrays dictionary.The Association that you create will end up in the projection metadata on the PurchaseOrderLinesPart entity (array) not on the TrackingInformation. So when you add the list for TrackingInformation to your page Bindname: <element you bind to> i.e., PurchaseOrderLinesPartList Property: <relation> i
Short answerThe absence of the datasource attribute on groups is not a defect. A group can not be populated with an array (multiple records). It has to be bound to either a selector, singleton or list that provides only one record. Long answerBasically, there are some main usages for a Custom Entity (Custom LU)Stand AloneA customer wants to collect and store information about something that is unrelated to other application data. Let say this is a list of office equipment. A custom entity is created together with a custom page. With this the customer can use the page to enter equipment.ReferenceA custom entity may hold information that you want to connect to another entity as a reference. From above we assume that the customer wants to connect a person in the application to a specific item from the office equipment entity. To do this a custom attribute is added to the standard person entity. This attribute is of type reference and references the custom entity. This custom attribute is
With the release of 23R1 conditions are now enabled (not editor) in the Page Designer. In the places where you have attributes of type BooleanExpression it is now possible to input conditions, e.g., visible, required, editable.See https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/200_client_configurations/310_conditional_fields/#conditional_valuekind regardsTobias
With the release of 23R1 conditions are now enabled (not editor) in the Page Designer. In the places where you have attributes of type BooleanExpression it is now possible to input conditions, e.g., visible, required, editable.See https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/200_client_configurations/310_conditional_fields/#conditional_value
It seems that you have not specify what it is you do with the list and what it is that you mean with “does not work”
-Of topicNot an answer to the original question. I just post this because a big portion of this thread have been about global or not. So I just add a small note around this. If there are further inquiries about that. I suggest you start a new separate thread for that. @ShawnBerk - With the rebase tool introduced in 23R1, you will now see what changes IFS have made. Well not every change but the changes that IFS made in the client for the same artifacts that you have configured. This also means that you get to “merge” your configurations with the delivered changes.
The answer to the original question is that there is no current application support to move Page Configurations between context. So besides database scripts or manually modifying ACP’s (Not recommended, nor supported), the only way is to manually re-create the configurations in the wanted context.
Yes Navinth is correct. With the current design you connect a client model to the ACP. All configured artifacts for that model, regardless of context tag, will be included in the export.
@Joakim Fransson I believe that you where playing around with list view and mobile, is this question in that area?
Hi, Last answer from me arrived after your next question and because of that looks a bit strange. However I again have to say I’m sorry. I don’t know all aspects around marble and how you go about to build a layout according to your wishes. Two typical questions are: Q: Is it possible to build something like this? A: Configuration is a subset of marble. So the best way to validate if something is feasible to build is to build it in marble. If you can, then it is possible that it can be done in configuration, and if you can’t, then you could not do it in config either. Q: How to a build something in config. A: If you build it in marble, you could inspect it in the page designer to see how you would need to set it up. A1: Do you have an application example of what you try to do? Then go to that page with page designer and see if you can figure out the solution that way. The reason for me to refer to marble here is because configuration with (page designer) has always been intended for
I’m sorry I don’t know exactly what you’re asking. If the question is if you can create a page. Then the answer is yes. The page designer do not have the full capabilities compared to marble ( tailor on the inside, using developer studio). But to some extent it is possible to build pages from scratch. Kind regardsTobias
Short answer is no, you can’t create a dialog or an assistant using configuration (page designer). There are technical and design limitations that are the reason behind that. All the details around that fact is a far longer story though. For the expense and time examples you give. The application provides the assistant with the various steps that you can then tweak to some extent. Building a new dialog or assistant from scratch is another matter. For this you should use customization (extend on the inside)Kind regardsTobias
Just to second Martins answer. Current released versions of the Page Designer will only support boolean values for all FndExpression types. This means that it is not only tabs but any attribute that could hold an expression according to the metadata schema. E.g. visible, editable, readonly, required. We do have in the backlog to provide a condition editor and when that is in place. All those attributes will automatically also support conditions in the page editor. The exception to this rule is where there are expressions set by core. In these situations the expression is visible and editable as is. However this is only because the expression can not be shown as a boolean value. To edit the expression like this is however not supported and thus not recommended. /Tobias
Addition to answer from @EntNadeeL See: Map a custom context to a user group or user, inhttps://docs.ifs.com/techdocs/21r1/Foundation1/060_tailoring/220_Configuration/260_context_based_configuration/default.htm
Navinth is correct. It is not possible to disable export as a concept or remove the export command using the page designer. These are general commands that framework adds in runtime, and are not part of the page layout metadata.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
