Fields "mandatories dynamically"

[rengit62]

Hi Lab !
In a situation like this :

the xml is wrong because it lacks OPT-300-Procedure-SProvider.
And there are many of these situations.
How do you manage this problem with sdk ?
Of course I could write a simple javascript function, but this would be opposite to metadata-driven applications concept
Bye
Renato

[rouschr]

We call these "dynamic rules" or "conditional rules", ...
For example for OPT-300-Procedure-SProvider the condition (in fields.json) is:

...
  "assert" : {
    "value" : "{ND-Root} ${TRUE}",
    "severity" : "ERROR",
    "constraints" : [ {
      "condition" : "{ND-ServiceProvider} ${OPT-300-Procedure-SProvider is present}",
      "value" : "{ND-ServiceProvider} ${every text:$provider in OPT-300-Procedure-SProvider satisfies ($provider in /OPT-200-Organization-Company)}",
      "severity" : "ERROR",
      "message" : "rule|text|BR-OPT-00300-0251"
    } ]
  }

This is in the EFX language, thus this is part of the meta data as it is part of fields.json
EFX is a language specific to the SDK.

For dynamic rules you can use EFX. We have plans to demo this later in the editor demo (either fully using JS or on server side), but you will have to be patient for that because many other things will take priority.
EFX rules can be evaluated directly in the browser using javascript (not very easy ...) or on the server side using Java/C#... & XML/XPATH (easier). We provide a Java implementation to evaluate EFX: https://github.com/OP-TED/efx-toolkit-java
If you do not use Java on the server side you could also just have a little service running Java and call it from your server, that would be the simplest option.
There are also features foreseen for giving better feedback in the UI using only CVS (parsing svrl, and reading a custom report on the client side).

[rengit62]

Thanks !
Ok for the SdkSymbolResolver instead of the SymbolResolverMock , but I found only one implementation for TranslatorDependencyFactory

Am I missing something ?
Bye !
Renato

[rouschr]

You can find a dependency factory implementation in the viewer project: https://github.com/OP-TED/eforms-notice-viewer

package eu.europa.ted.eforms.viewer;
...
public class DependencyFactory implements TranslatorDependencyFactory {

[elerik]

Hi
i wrote that "simple javascript" which dynamically solve it in real time (for most of it)
during rendering i insert attribute for mandatory and forbidden conditions if they have some (assert i dont implement at this moment) and tag them as conditional-required.
Then i go through only elements with those attributes and solve them. Even with complex form its surprisingly not so much elements so its pretty fast.
Then i evaluate efx condition via javascript and adapt element requirements It wasnt so simple how i thought it will be.
for example most of elements are just part of groups so i evaluate firstly only elements in same group. then if there is none (in some cases) i expand this area of check to parent group and so on until its whole form (rare situations)
I have never met efx so i evaluate those "string conditions" in my own. There are i guess some libraries for that.

regards

[rengit62]

I am trying to put EFX conversion inside app ( application server wildfly ).
I copy DependencyFactory from https://github.com/OP-TED/eforms-notice-viewer, in project efx-toolkit-java .
I only commented (SdkDownloader.downloadSdk(sdkVersion, sdkRoot);) because of an error on MavenBooter

But here :

I got an error :

can you help me ?
Thanks and Regards

,

[rouschr]

I am not sure what your error is as I see no stack trace. Looks like it does not find something for the SCRIPT_GENERATOR as indicated by your screenshot but other things only show "Object...." so I cannot help you. A Java error logs with a stacktrace would be more helpful.
In the worst case you could manually git clone version 1.8.0 from the GitHub SDK project and put it into the sdks folder yourself if the problem is related to downloading from GitHub.
Also make sure to use the latest version of the editor demo project which now supports 1.8 "xsdSequenceOrder", later on it may only support 1.9, so always make sure you check the supported versions in application.yaml of the editor. Latest work on EFX toolkit may rely on data or features of 1.9, so make sure you have no mix of 1.8 and 1.9 between the used projects.

[rengit62]

Thanks Christophe
I've just got to a result, changing some classes, statements, but I would like to "consolidate" the result, without changing anything.

Some questions to begin :

1. you told me to get DependencyFactory class from https://github.com/OP-TED/eforms-notice-viewer, I put here in project efx-toolkit-java, it is right ?
   
   Will this class be put in the future in toolkit/core ?

2. compiling with maven I set 2 dependencies in our current project :

<dependency> <groupId>eu.europa.ted.eforms</groupId> <artifactId>efx-toolkit-java</artifactId> <version>${efx-toolkit.version}</version> </dependency> < dependency> <groupId>eu.europa.ted.eforms</groupId> <artifactId>eforms-core-java</artifactId> <version>${eforms-core.version}</version> </dependency>

Do you agree with level of project ?

About 1.8 I've already downloaded and I am using it.

3. let's consider for example :
   "condition" : {ND-ContractingParty} ${BT-11-Procedure-Buyer not in ('body-pl','body-pl-cga','body-pl-la','body-pl-ra','cga','def-cont','eu-ins-bod-ag','grp-p-aut','int-org','la','org-sub','org-sub-cga','org-sub-la','org-sub-ra','ra')}

about context , of course I can split the string to find ND-ContractingParty and make the context, is there any method , or class that is present in toolkit/core to get the context, or at list the first string (ND-ContractingParty) ?

Bye
Renato

[rouschr]

Hello,
I never said to get or copy Java files somewhere, you can see how this works by looking at EFX toolkit or the viewer project. From there on you have to use your Java knowledge.
For EFX conditions, you should use the EFX toolkit.
For EFX templates, you should use the viewer (see view-templates .efx files of the SDK).
For both the core project provides some classes.
In the toolkit project we extend the SdkComponentFactory of the core project, I think in previous answers I forgot to mention the core project: https://github.com/OP-TED/eforms-core-java/blob/develop/src/main/java/eu/europa/ted/eforms/sdk/component/SdkComponentFactory.java
I recommend that in general you look into junit tests (look for @Test) of the projects as this shows you how the code can be run to evaluate expressions, for example in EFX toolkit see:

class EfxExpressionCombinedV1Test extends EfxTestsBase {
  @Override
  protected String getSdkVersion() {
    return "eforms-sdk-1.0";
  }

  @Test
  void testNotAnd() {
    testExpressionTranslationWithContext("not(1 = 2) and (2 = 2)", "BT-00-Text",
        "not(1 == 2) and (2 == 2)");
  }

  @Test
  void testNotPresentAndNotPresent() {
    testExpressionTranslationWithContext("not(PathNode/TextField) and not(PathNode/IntegerField)",
        "ND-Root", "BT-00-Text is not present and BT-00-Integer is not present");
  }
  ...

[rengit62]

Hi
for now we are interested to expression, only.

in https://github.com/OP-TED/efx-toolkit-java
it is written :
**The EFX toolkit requires Java 11 or later.

It is available as a Maven package on Maven Central and can be used by adding the following to the project's pom.xml.

... ` eu.europa.ted.eforms efx-toolkit-java ${efx-toolkit.version} ` ... **

and nothing else.

As the junit tests you are written about, use the class DependencyFactoryMock, are you going to put on toolkit an implementation of TranslatorDependencyFactory that use the real fields.json and codelist ?
Best Regards

[rouschr]

Hello, I do not think we will do that in the toolkit, but as said in another answer, something similar is done in the viewer, there the SDK is used. For SDK download automation see usage of https://github.com/OP-TED/eforms-core-java/blob/develop/src/main/java/eu/europa/ted/eforms/sdk/resource/SdkDownloader.java
You can also just download SDK files manually and put them in a folder for a start, but we recommend you use the SDK downloader. The viewer uses it.