Forum Replies Created

  • Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    1
    Down
    ::

    Hi Klaus,

     

    you are absolutely right about this. Screen titles as of now are not translatable in Simplifier and its value will be statically taken from the UI Designer. We will create an internal feature request so that our core implementation team can evaluate your requirement and add the translation functionality to Simplifier in an upcoming release.

    Thank you for your feedback!

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hi Christopher,

     

    you are right, as of now this is a typical use case that has to be implemented inside of a client-side business object function (or a script activity, if you prefer to use that). Unfortunately server-side business objects (SBO) don’t support JavaScript Promises yet, but this is subject to change in a future Simplifier release where we plan to update the JavaScript engine of SBOs to make ECMAScript features of versions higher than 5.1 accessible. Please keep a close look on our changelog for that matter.

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hallo Timo,

    könntest du bitte mal prüfen, ob in der betroffenen App die Funktion “Automatisches Binden” aktiviert ist oder nicht? Du findest diese Einstellung über einen Klick auf den Applink im Application Editor (siehe Screenshot 1). Für Widgets in der OpenUI5-Version 1.60 müsste diese deaktiviert werden, damit Bindings von Aggregationen korrekt funktionieren (siehe Screenshot 2).

    Das automatische binden ist seit Simplifier Version 5.5 standardmäßig deaktiviert, sobald man neue Apps erstellt. Aus Rückwärtskompatibilitätsgründen zu Bestandsapps, die auf Basis einer älteren Version als 5.5 erstellt wurden, ist die Funktion jedoch immer aktiviert, da dies dem vorherigen Stand entsprach, wie die App-Sources generiert wurden beim Deployment. Diese Einstellung auf “aus” zu stellen wirkt sich positiv auf die Ladezeiten von Applikationen aus, da dadurch Model-Bindings nur dynamisch zur Laufzeit initialisiert werden, wodurch diese mittlerweile Standard geworden ist.

    In unseren Standard-Widgets der Version 1.60 wurde für alle Aggregationen zusätzlich noch eine Eigenschaft (“templateShareable = false”) verändert, die im Zusammenspiel mit der nun deaktivierten Autobind-Funktion relevant ist. Da du berichtest, dass die 1.44er Widgets noch zu funktionieren scheinen, wo die Eigenschaft für die Aggregationen noch nicht den veränderten Wert (“templateShareable = true”) trägt, sieht es für mich so aus, dass eben das “Automatische Binden” den Fehler verursacht und somit das items-Binding für die ComboBox nicht mehr funktioniert.

     

    Viele Grüße,

    Armin

     

    Attachments:
    You must be logged in to view attached files.
    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hi Klaus,

     

    just like Kahn mentioned, I was able to adapt your BO function writeLogEntry inside of the BO DB_Log so that it outputs the error message received from the failed connector call. While the error object e itself is undefined, the message itself can indeed be accessed and printed out as a log. I left the necessary line of code in the BO script for you but commented it out, hope this helps you.

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hi Klaus,

     

    what Mathieu meant was to build the whole SQL statement dynamically inside of a business object script and then pass it to the request parameter of your SQL connector call which must then be left blank in the respective creation dialog field. Basically this will give you the option to treat the SQL statement like an input parameter instead of the request getting taken from the SQL tab of the creation dialog.

     

    Hope this clarifies Mathieu’s suggestion.

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hi Ksenia,

     

    as your output seems to be of a collection type (which resembles a Javascript object), you can also navigate directly into your output structure when specifying the output parameters in your SQL connector call. However, this will only work, if the field you want to access within your output has a static position, e.g. it is always part of the first object included in the array under the same key, no matter the input of your SQL query. Then you could specify your output parameter like the following:

    /[indexInArray]/keyInObject

    What you see above is basically the path to the field within your structure, starting from the very top (which is the “/” or root, respectively). Please remember to adapt the data type of your output parameter accordingly as you won’t get a collection returned anymore but the simple datatype of the field itself, like string or integer.

    If the position of the value within your output structure should not be static, I would suggest to access it dynamically from within a business object that executes the connector call. Here is how to achieve this. Using the business object is of course not really different from your script-based solution, so please keep that in mind.

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hi everybody,

     

    unfortunately in the meantime SAP has changed the accessibility of their Theme Designer again, therefore we have adapted our instructions on how to be able to use the Theme Designer. Please refer to this article from now on: https://community.simplifier.io/knowledge/using-sap-ui-theme-designer/

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hi Klaus,

     

    using the server-side business object API you can access the output of a connector call with the following notation: Simplifier.Connector.<ConnectorName>.<CallName>(payload?: string|object). Of course you already seem to know this. However, on top of that you can access all the parameters via the usual Javascript dot notation of an Object, as it’s this type that is returend by the already mentioned API call.

     

    Let me adapt your code snippet to make this more clear:

    lastname = Simplifier.Connector.Attributes.connectorCallXYZ({}).AliasOfParameter1;

    firstname = Simplifier.Connector.Attributes.connectorCallXYZ({}).AliasOfParameter2;

    So if you have a second parameter you can simply assign it to a second variable by accessing that key of the returned object of the connector call API. This would be exactly the same if you would query another business object instead of a connector of course. Hope this makes it even easier for you in the future. Please take note though that the keys in this object will only be meaningful if you specified an alias for each parameter in the corresponding connector call. If you did so, the keys will be the aliases that you specified.

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hi Shivam,

     

    we regard this topic as a duplicate of this one: https://community.simplifier.io/forums/topic/file-object-not-showing-in-postbody-of-rest-connector/ Please refer to the other topic for an answer to your problem, thanks!

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hi Shivam,

     

    we regard this topic as a duplicate of this one: https://community.simplifier.io/forums/topic/file-object-not-showing-in-postbody-of-rest-connector/ Please refer to the other topic for an answer to your problem, thanks!

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hi Shivam,

     

    we regard this topic as a duplicate of this one: https://community.simplifier.io/forums/topic/file-object-not-showing-in-postbody-of-rest-connector/ Please refer to the other topic for an answer to your problem, thanks!

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hi Shivam,

     

    unfortunately you won’t be able to use Simplifier’s REST connector for this use case as it does not support multipart as of now. This limitation is known to us and will be eliminated in a future Simplifier release. However I cannot provide you with an exact due date for this enhancement yet. Please check the changelogs of the upcoming Simplifier releases to see if multipart support has been added to the REST connector.

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    1
    Down
    ::

    Hi Fulya,

     

    I created a small example application for your use case which you can download from here and then import into your instance: https://files.simplifier.io/f/6bce84879ee346eeb72b/?dl=1 . To download the file, you need to enter the password “simplifier”. Please take note that the download link will only be valid for 30 days.

    In the application I added a sap.m.Input widget to a screen and added a ui.core.Item to the suggestionItems aggregation of the sap.m.Input. The ui.core.Item serves as a template which will be copied as often as there are elements returned from your data source which are bound to the suggestionItems aggregation. My data source in this case is a server-side business object (BO) which returns the whole JSON that you provided. What I’m doing to make sure that the output is in the correct format is that I’m directly returning the array holding the possible values for the street name under the parameter name “suggestions” by navigating to the streets field within the JSON. Please look up the parameter name field in the output parameter panel of the business object function “getSuggestions” as reference. With doing so, I can directly map the outputted collection of the BO and its included structure onto the aggregation and its template item in the Process Designer. Of course I had to configure my sap.m.Input widget in the Designer first, what I did was the following steps:

     

    – set suggestionItemsTemplate to true

    – selected the collection data type that is configured in the BO for the suggestionItems aggregation

    – set showSuggestion to true

     

    Now, when running the application, the BO is called on start and the JSON output mapped onto the suggestionItems aggregation. If I input “Ehre”, it will display the matching results in a popup on top of the sap.m.Input.

     

    Hope this helps you! Please let me know if there’s any questions left.

     

    Regards,

    Armin

     

    Edit: I forgot to tell you, why I didn’t use the suggestionRows aggregation but suggestionItems instead: As you can read here https://sapui5.hana.ondemand.com/#/api/sap.m.Input%23aggregations suggestionRows is best used when you want to display suggestions in a tabular manner. I don’t think this would fit your use case though since you only have one specified value that you want to display per entry. Thus suggestionsItems is the appropriate solution.

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    1
    Down
    ::

    Hi Patrick,

     

    yes you’re right, OpenUI5’s ID scheme is always built up like this in the DOM: “ScreenId–WidgetId”. Therefore, if you’re using the byId function from the core element of OpenUI5 as in the above example, you have to prefix the id of the current screen you’re on inside of your application and then use two minuses as a separator from the widget id as well. However, there are more ways to access a certain screen element which don’t require you to prefix the screen id anymore:

    – From the screen object: sap.ui.getCore().byId(“ScreenId”).by(“WidgetId”)

    – Using “this” (important note: usually the “this” object that you can access from a script within the Process Designer of Simplifier will return the current screen’s controller; please keep in mind though that “this” might be something different depending on the scope during runtime, e.g. inside of a callback function): this.byId(“WidgetId”) or alternatively this.getView().byId(“WidgetId”)

     

    Hope this helps you to be a bit more flexible in accessing screen elements via script.

     

    Regards,

    Armin

    Armin
    Moderator
      Has successfully completed the online course No-Code.
      Has successfully completed the online course Low-Code.
      Has successfully completed the online course Pro-Code.
      Has successfully completed the online course Basics - 100.
    • Topics: 0
    • Replies: 58
    # 1 year ago
    Up
    0
    Down
    ::

    Hello Christopher,

     

    yes indeed there is an update! I can confirm that with the upcoming Simplifier 6.0 release due end of January ’21 this feature will be included in the Simplifier mobile client. Currently it is part of our development roadmap and will be implemented very soon.

     

    Regards,

     

    Armin

Viewing 15 posts - 16 through 30 (of 53 total)