This content has been marked as final. Show 12 replies
The previous poster is correct in that a system externally accessible is a part of the process of setting a system up to be available on mobile.
I believe you can write an application yourself using Oracle ADF, but I'm not sure of the licence implications when you move it to production. If you're interested in commercial solutions, then if your requirement is putting a mobile layer on top of a specific component, or a small set of components, then the company that I work for, Succeed Consultancy (http://www.succeed.co.uk) , would be a good place to start.
If you're after a product that can mobile enable your entire system, then Grey Heller's PeopleMobile (http://greyheller.com/Products/people-mobile.html) product is also one that's used by many clients.
Hope that helps.
I'm not aware of many good online resources that tell you how to create your own mobile app from a PeopleSoft Component, but I can give you an overview of what it takes.
There are a couple of options:
#1 You can use CI based web services to generate a WSDL for a component. Then you can use any development tool to consume the WSDL and create a mobile application. If you have a .net development team, then .net would be an approach. If you have Ruby developers, then they might prefer ruby/rails. If you have a Java team, then JDeveloper's web service data control and ADF drag/drop development is one method. My book has a chapter that shows how to do this. This is also the approach taken by the mobile inventory application available with PeopleSoft.
#2 You can use iScripts or REST based services to serve a mobile application directly from PeopleSoft or Integration Broker. The new mobile company directory, mobile approvals, etc use the iScripts approach. This approach allows you to write PeopleCode to send/receive data from/to a CI. You use HTML definitions for forms/HTML, etc. It is not drag and drop, but often gives you a very nice mobile UI because you can easily use jQuery mobile to create the user interface.
Both options 1 and 2 are for web based mobile apps.
#3 Create device specific mobile apps that use CI based web services or other PeopleSoft non-CI web services that use CI's on their OnRequest handlers. This is the approach taken by the older iPhone iReceipts expenses application.
Basically, PeopleSoft applications provide the backend infrastructure/plumbing and it is up to you and your team to decide what approach works best for you. It is very flexible.
We have created a mobile app for self services by using CI. And it is working nice. Now my question is can we resale this app in the open market? is there any license implication?. I have two good resources for Android and iOS technologies , and always think on this option.. I mean creating a Mobile app and sale it
I am glad you have it working. That is great!
In regards to licensing for resale, I know a lot of people sell mobile apps and other custom content/collateral through consulting engagements. I really don't know what is required to make this happen. You might contact one of the other mobile app sellers, such as Grey Heller to see if there are any licensing requirements.
I search on net and found that not every component is fit to be used as component interface. PO & Vouchers are large components with a lot of entry fields and consist of several pages, which would make the web service request huge and complex.And I am only talking about entry, not talking about the approval of submitting/matching.Also be aware of that PeopleCode sometimes will not execute when called from a Component Interface, usually think time functions.
Meaning PeopleCode can execute differently when called from a Component Interface.
If you want to create mobile pages, you should have as less as possible data entry fields, especially if you also want to enable it on cell phones.
For example, try entering a PO/Voucher from your tabled and notice the difference/discomfort compared to a PC.
That is why PeopleSoft has developed Mobile Expenses and Approvals, with minimum data entry, using iScripts that can call Component Interfaces for data entry and jQuery for styling it for Mobile. Also, we can also create mobile solutions for PeopleSoft with Oracle ADF (Mobile), as mentioned for Mobile Inventory.
So, to overcome all, Oracle is pleased to announce the release of new applications, PeopleSoft Mobile Expenses and PeopleSoft Mobile Approvals, which are now generally available in PeopleSoft FSCM 9.1. These are the first two of many upcoming applications designed and built to cater directly to the mobile workforce by providing user-friendly access to key business functions on a smartphone or tablet.
"So, to overcome all, Oracle is pleased to announce the release of new applications, PeopleSoft Mobile Expenses and PeopleSoft Mobile Approvals, which are now generally available in PeopleSoft FSCM 9.1. These are the first two of many upcoming applications designed and built to cater directly to the mobile workforce by providing user-friendly access to key business functions on a smartphone or tablet."
I believe these apps are HTML 5 based not Native Mobile OS.