Links may not function; however, this content may be relevant to outdated versions of the product.
Guidelines for using custom modules with the Mashup SDK on iOS in Pega 7.2.1
iOS developers can extend the functionality of their third-party mobile applications that contain Mashup SDK functionality by also using custom modules that are developed in Objective-C. Custom modules enable third-party mobile iOS applications features and functions directly in Pega 7 Platform mobile apps that use the Mashup SDK.
To develop custom modules for the Mashup SDK in your native third-party mobile iOS application, do the following tasks:
- Read prerequisites
- Import the iOS custom module template
- Add third-party dependencies
- Extend the app with plug-in classes
- Extend the app with extension classes
The native iOS mobile app that uses the Mashup SDK must be developed by using these tools:
- Objective-C programming language
- Xcode 7.2 or later. For more information, see Xcode features.
Make sure that you do the following tasks:
- Read the Mashup SDK overview article.
- Download and install CocoaPods 0.38.2 or later.
- Read the Technical overview section of the Developing custom modules for iOS article, which describes the supported structure of custom modules for the Mashup SDK.
Import the iOS custom module template
Prepare the module by doing the steps in the Importing the iOS custom module template section of the Developing custom modules for iOS article. Keep in mind that:
- In step 2, after extracting the distribution package, the Examples/Modules directory of the *.zip file contains a directory with four sample custom modules.
- To create your own custom module, copy one of the sample custom module directories and modify its contents. The name that you choose for the directory must be identical to the name of the module used throughout the procedure.
- Remember that you include your custom module in the Xcode environment by adding it as a regular pod to the Podfile. For more information, see Podspec Syntax Reference. For example, a new entry in the Podfile could look similar to the following entry:
pod 'myCustomModule', :path => '../Path/myCustomModule'
- Skip step 5, because compiling the custom module is not necessary. After you add the new pod to the Podfile, remember to run
pod installin the project folder and use
Add third-party dependencies
If applicable, you can also add third-party dependencies to your custom module. Follow the instructions in the Adding third-party dependencies section of the Developing custom modules for iOS article. Skip the step that states to run the Ant command, because it is not necessary.
Extend the app with plug-in classes
Follow the instructions in the Extending the client plug-in classes section of the Developing custom modules for iOS article. Skip the instructions that describe testing the module.
Extend the app with extension classes
Follow the instructions in the Extending the client with extension classes section of the Developing custom modules for iOS article.