Recommended approach

You might consider requesting access to an IFS RACE environment, then develop your Apps 10 solution against that. That will get you closer than developing against your old Apps 8 environment, since the application connectivity changes drastically between these versions.

(This is assuming you don’t need to report against customized or configured data.)

Hi Kevin, thanks for your response! That could be a good idea, but would you be so kind and provide a little more information (indicative/lead) about the RACE environment, please?

Unless something changes recently, Apps10 Race environments are hosted, i.e. not something you install yourself. 

You would need to contact IFS to request one to be setup/made available to you.  I would start with your company’s IFS customer partner (whoever that is) who should be able to help you.  You could alternatively put in a request to IFS Support and they can likely assist.

Nick

Thanks to you too, Nick!

Even though it’s good to be aware that such features exist, our temporary conclusion is that an environment which doesn’t involve/allow custom data would be of limited value to us.

Subsequently we’re back at where this thread started: Even though we (or rather ‘that other’/the main implementation project) have hooked up with a couple of local/national/regional SIs (System Integrators) who BTW involve skilled former IFS employees, we quickly end up in a fragile situation where we have too few personnel with sufficient insight into the sometimes 2nd or 3rd level implications of design choices available to our team, i.e. a significant project (possibly even enterprise) risk.

The fact that IFS has moved onto a more open ReST API-centric path helps a lot, but we don’t see the scarcity of competencies vanish anytime soon.

My two cents of personal opinion says that even though IFS invests in their ‘Aurena’ client, a Swagger-like kind of API documentation would help A LOT when customers like ourselves need to expose features/datasets from within IFS A10 over to other systems in an application-to-application (A2A) fashion – not just purposed for use case scenarios where there are human eyeballs involved. Along with artefacts such as the underlying data model being made available to this community. So far I haven’t found any of that, and thus keep stumbling around.

/A.

“My two cents of personal opinion says that even though IFS invests in their ‘Aurena’ client, a Swagger-like kind of API documentation would help A LOT when customers like ourselves need to expose features/datasets from within IFS A10 over to other systems in an application-to-application (A2A) fashion – not just purposed for use case scenarios where there are human eyeballs involved. Along with artefacts such as the underlying data model being made available to this community. So far I haven’t found any of that, and thus keep stumbling around.”

I agree.  From last year’s World Conference it looks like making APIs better available for a2a is something they are moving into quickly, but I don’t know where the documentation for this resides today (if anywhere).  My guess is that they will have something available sooner rather than later because it will be needed for the approach to succeed, but who knows what timeframe that might be?

Nick

I THANK you Jeannine,

This served as a quite useful confirmation. We’ve been hoping for/expecting a direction like this, but so far haven’t come across too much «proof» or validation. Membership in the OpenAPI Initiative is precisely the kind of stuff we’d like to see! :-)