1. David Hepburn
  2. PowerServer Mobile (Obsolete)
  3. Thursday, 27 September 2018 21:53 PM UTC

I've come to a point where I need to get serious about the PB2017 Appeon Workspace and which way to go. Up till now, this week in fact when the Appeon Apple provisioning profile expired for our existing PB12.5 environment and apps.

We have been using a Workspace on our server original supplied by Appeon but is no longer supported (or supplied). This has worked well, until it expired yesterday. Now, we have converted apps to PB2017 but have the issue of no workspace. For now, we get our users to download the workspace from the App Store, and have them add our app into that. This works fine.

My question is, do you see any negatives in doing this? Should we continue on this path? I know you can build your own workspace but requires an Apple PC to do all the Xcode stuff, which we don't have. It also seems very involved and complicated.

Your thoughts?

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 28 September 2018 13:59 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 1

Hi David;

     As another side note to this discussion and around your point on mismatches. This has been a problem for most software vendor tools from the likes of: Sybase, Oracle, IBM, Microsoft, etc. After 30+ years in the IT industry, this is where I learned the value of System-To-System controls! They have saved me many hours/day/weeks of headaches (and stress) preventing possible issues and pinpointing right away all the weird things that can happen to a production App (the stories I could tell you).

    That is why S2S controls are at the heart of my frameworks. They detect many out-of-balance conditions and report/log/email/etc these conditions to developers and production support personnel before an App or Web Service starts. In your case, this would apply to your use of PowerServer based Apps - whether they be Web or Mobile. Here is an example of the S2S control settings for AWS & PS in the Integrated Framework. I have highlighted in bold the items relevant to PS based Apps as follows:

;  ----- Start System Control Section. ----
;  ----- End System Control Section. ----


    At run-time, all these S2S checks are performed and if one is non-compliant ... the user & support personnel will be notified. For the developer, it could be just a simple message dialogue, for example:

    In production, you can let the framework know if it should stop the user from continuing or if it optionally could allow them to continue with this error. Either way, the proper people are notified and the decision is logged as well for further resolution by application support. For example:

  The S2S controls have really proven their worth to me in any development language that I have ever used. This approach has proven itself in the mainframe, mini and now PC worlds. As most PB developers know, an out-of-balance run-time or peripheral connected App pieces are critical to the proper operation of any App. Running with mismatched software is typically a "ticking time bomb"!

   Please feel free to adopt any or all of the S2S controls from the Integrated Framework as the framework is free & open source.


Regards ... Chris



There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 27 September 2018 23:20 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 2

Hi David,

I don't think this is a good approach because the Appeon Workspace on the app stores under Appeon's account are for demo purposes only, and so we are always updating them to the latest version.  Your PowerServer version may be lagging behind the version of Appeon Workspace on the app store, which could create problem due to version mismatch.

I think the best approach would be that you create your on Appeon Workspace.  The packaging wizard will generate necessary project files for you to use Google or Apple tools to compile to .APK and .IPA respectively. 

Once you have .APK and .IPA files you can decide if you want to distribute your customized Appeon Workspace privately or if you want to post it to the app stores.  If privately you will need to apply for an "Enterprise Certificate" from Apple, and I believe cost is $299/year.  https://developer.apple.com/programs/enterprise/how-it-works/ 



  1. David Hepburn
  2. Friday, 28 September 2018 03:23 AM UTC
Yep - I gather that was always an issue. However, I was going to try to make some sort of reminder for staff (it's an internal app) to never update the Workspace from the App Store, unless I instruct them to. I know some will anyway and I will have to deal with it then but it raises the question, will the app still work if there is a new release on the app store and the user hasn't updated it? Is there some sort of check Workspace does and detects a new release and therefore stops working until the mobile has been updated?

Another thought - why can't Appeon make the Workspace backward compatible so even if there is a new release and is installed, apps compiled under an older version still work. Pretty much a standard with any other software right?
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Friday, 28 September 2018 18:39 PM UTC
There is no hard restriction that stops a particular version of the Appeon Workspace from working, and in general we maintain backwards compatible communication protocol/API between the Appeon Workspace and the PowerServer. But the JavaScript generated by PowerBuilder may be mismatch with what a newer version of Appeon Workspace needs to function properly so you could experience granular issues within your app.

We could make it backwards compatible, but then the Appeon Workspace would get huge. We are fairly agile in our development cycle, so just over few years time there would be dozens and dozens of Appeon Workspace libraries embedded in the one download. Also, there would be need to be complete redesign of the Appeon Workspace internals to do such switching and avoid memory conflicts. So I think chances are low we would do this.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.