Home Forums Development Using data from other fields in an AFL portlet.

Viewing 6 reply threads
  • Author
    Posts
    • #22032
      Max WidmaierMax Widmaier
      Participant

      Hello all!
      I’ve recently discovered AFL portlets. These seem to be a very powerful tool, but there seems to be very little documentation on what it’s capabilities are (using in-built functions of course). I was wondering if it were possible to grab the data from other fields in the portlet and use them for calculating new fields, running data operations, parsing, etc.
      For example,

      Obviously, I could achieve this through using React, however it would be far simpler to just use an AFL module because it already has the look and feel of Finance. So, is there a way to get the value of a field in the portlet or will I just have to use React? If any exists, could I be pointed to further documentation on various functions and abilities of AFL portlet other than the basic documentation here

      0
    • #22042
      Max WidmaierMax Widmaier
      Participant

      Also if I’d like to use other JavaScript libraries in my portlets how would I include them? For example, jQuery.

      0
    • #22079
      Ed ShawEd Shaw
      Keymaster

      Max, I’ve attached a PDF with some more information about AFL. This document will be included in our public documentation set in the near future. Thanks

      0
    • #22086
      Ed ShawEd Shaw
      Keymaster

      File seems to be too large for the server upload. I’ll send it directly to you.

      0
    • #22095
      Max WidmaierMax Widmaier
      Participant

      I’d just like to check because this may be an issue, but can I use Typescript while developing stuff (as long as I package it before running?). I assume that would be fine but just checking.

      0
    • #22104
      Ed ShawEd Shaw
      Keymaster

      Max,

      For very custom portlets, there are examples in training for how AFL and also AFL/React may be integrated and done carefully, they have their uses. That said, the vast majority of UI patterns can be accomplished in NexJ Studio using MDA Layouts, Portlets, and Dialogs.

      Using raw AFL and including 3rd party libraries and tooling is not the recommended approach as we don’t have predictability of security, download size, compatibility, licensing … You also have to do a fair bit of manual work to support data binding, internationalization, rendering, context sharing and ongoing maintenance.

      Please confirm with your project team what you plan on doing with AFL and what the plans to maintain that code going forward would be.

      Thanks

      0
    • #22124
      Max WidmaierMax Widmaier
      Participant

      Unfortunately, I don’t think there is a way to do that with MDA. Unless there’s a way to easily parse text using scheme. I was mostly asking about JavaScript APIs because I wanted to ensure that we could use a library I am building which provides an abstraction layer over Finance’s REST API. Unless there’s a way to interact with the database using AFL, which I haven’t seen, that will be necessary for ease of programming and code readability. The reason I’m using AFL is because JavaScript is because it is easier to process data, especially for the specific task we are using it for. So it wouldn’t be 3rd party libraries because we’d be developing it in-house. I will take a look at training however.

      Thanks

      0
Viewing 6 reply threads
  • You must be logged in to reply to this topic.