Welcome, we are now Quest! Learn more about Support at Quest

Mobile IT 1.3 - SDK

Welcome
What's New in Mobile IT 1.3 What's New in Mobile IT 1.2 What's New in Mobile IT 1.1 Mobile IT SDK Reference Quest.Cyclone.Interfaces Namespace
ActionResultDisplayType Enumeration Alert Class AlertActionArguments Class AlertActionDefinition Class AlertActionRequest Class AlertActionResult Class AlertActionState Enumeration AlertBasicProperties Class AlertChange Class AlertExtendedProperties Class AlertId Class AlertSeverity Enumeration AlertStatus Enumeration ArrayDatasheetParameter Class BooleanDatasheetParameter Class CaptchaDatasheetParameter Class ColumnVisibility Enumeration ComponentStatus Class ComponentStatus.PluginState Enumeration ContentSearchType Enumeration CustomField Class CustomFieldType Enumeration Datasheet Class DatasheetAction Class DatasheetActionCategory Class DatasheetColumn Class DatasheetContent Class DatasheetMessage Class DatasheetMessageSeverity Enumeration DatasheetOperationState Enumeration DatasheetParameter Class DatasheetParameterGroup Class DatasheetRecord Class DatasheetResponse Class DatasheetResponseType Enumeration DateTimeDatasheetParameter Class DateTimeDatasheetParameter.UsageKind Enumeration IAlertingService Interface IAlertProvider Interface IComponent Interface Icon Class IntegerDatasheetParameter Class IPackageParameters Interface IReportProvider Interface IStatusProvider Interface MultiselectDatasheetParameter Class Range Class RelogonInformation Class RelogonType Enumeration RequestContext Class RequestProperties Class SecureStringDatasheetParameter Class StaticTextDatasheetParameter Class StringDatasheetParameter Class SwitchDatasheetParameter Class UserCredentials Class
Legal Notice Quest Software Corporation Contact Us
Third Party Contributions

Welcome


Quest Mobile IT SDK Reference
Welcome
See Also 

Welcome to Quest® Mobile IT SDK

Quest Mobile IT is a comprehensive solution for remote system management. It allows keeping different target systems under control using mobile device connected to the Internet or local network. Support for a specific target system is provided by the corresponding software package known as a Mobile Pack. Mobile Packs can be obtained at Mobile IT Community and Quest Online Store. In addition, Mobile IT has its own software development kit (SDK) using which you can create your own Mobile Packs to support desired target systems. Mobile IT provides two ways of introducing custom Mobile Packs:

  • Creating custom Mobile Packs based on .NET components

  • Using PowerGUI® PowerPacks

Note

Custom .NET Mobile Packs are not supported in the free version of Mobile IT. Consider buying Mobile IT developer license if you need that functionality.

Creating .NET Mobile Packs

You can create your own Mobile Packs based on .NET components. Such Mobile Packs can support both alerting and reporting functionality. Creating .NET Mobile Packs is the best way to extend Mobile IT functionality and get all the benefits out of the platform. To get started, refer to the Creating Mobile Pack topic.

Using PowerGUI PowerPacks

You can use PowerGUI PowerPacks either created by you or downloaded from the PowerGUI community website in the same way as you use Mobile Packs. PowerPacks are able to provide only reporting functionality for target systems. To get more information, refer to the Working with PowerPacks topic.

See Also


Was this topic helpful?

[Select Rating]



What's New in Mobile IT 1.3


Quest Mobile IT SDK Reference
What's New in Mobile IT 1.3
See Also 

This section lists new features that are implemented in Mobile IT 1.3 SDK. It also describes differences between Mobile IT SDK versions 1.3 and 1.2.

What's New in Mobile IT SDK 1.3

  • The globally unique identifier of a requested datasheet content was introduced in this SDK version. This identifier enables user code to determine the collection of records that is being queried. For example, if the action resulted in getting a nested view, then a Mobile Pack can use the contentId to find that records from the current view are being processed or the user has returned to previous content and is trying to apply an action to a record from the previous collection. For more information, refer to the Generating Simple Datasheet topic.

  • New types of datasheet action: ActionResultDisplayType.Refresh and ActionResultDisplayType.LeaveAsIs. These actions let you update the current representation or leave it unchanged. For details, see Implementing Actions for Datasheet.

  • The number of content items that can be generated (through NestedView actions, see Implementing Actions for Datasheet) is not limited. You can now go back to a previously received content item using the regular back navigation and continue to run actions on any of the previously received content records.

    Note

    PowerPacks have partial support for this feature and require a refresh of the page when you go back to previous content.

  • This version introduces context-sensitive actions that help you work without selecting records. For details, see Implementing entire Datasheet Actions.

  • Comments can now be added for pack instance parameters. The new comment XML element is used for this. For an example of using comments, see Manifest File Format.

  • Pack description capabilities have been enhanced. You can now include Bulletin Board Code notation in descriptions. For an example of using BBCode, see Manifest File Format.

  • You can provide descriptions for datasheet parameters by setting the Description property.

  • For development and debugging convenience, pack configuration files are (*.config) are now kept for as long as the agent exists, until a newer version of the pack is installed. This extends debugging and fine-tuning capabilities, because the pack does not need to be recreated any more.

See Also


Was this topic helpful?

[Select Rating]



What's New in Mobile IT 1.2


Quest Mobile IT SDK Reference
What's New in Mobile IT 1.2
See Also 

This section lists new features that are implemented in Mobile IT 1.2 SDK. It also describes differences between Mobile IT SDK versions 1.2 and 1.1.

What's New in Mobile IT SDK 1.2

  • In Mobile IT 1.2 datasheet parameter support is significantly improved. New parameter types are introduced, as well as functionality of existing ones is extended. See the general changes below in this section. For more information, refer to the Using Datasheet Parameters topic.

    • New parameter types are introduced: StaticTextDatasheetParameter and CaptchaDatasheetParameter.

    • The DateTimeDatasheetParameter parameter now includes information about time zone.

    • There is now an ability to validate a parameter value and display customizable error message if the value is inappropriate.

    • Each parameter or a group of parameters can be assigned an identifier. It is internal and not displayed to user. This can help write clean and maintainable source code for Mobile Packs. For details, see DatasheetParameter and DatasheetParameterGroup.

    • For certain types of parameters, such as BooleanDatasheetParameter and SwitchDatasheetParameter, the so-called postback feature is now supported. When value of parameter with postback feature is changed, it is passed to Mobile Pack immediately even if other parameters of the same group are not specified yet.

  • Mobile IT SDK 1.2 has lots of enhancements related to the end-user experience as follows:

    • Now each datasheet (report) can have a text description which is displayed on a mobile device in addition to the title. For details, see Datasheet.

    • For datasheet items there is now an ability to configure whether to display the items only on details view of a datasheet or on both datasheet main view and details view. For details, see DatasheetColumn.

    • When displaying datasheet content on a mobile device, details view can be disabled. This can be useful when all descriptions of datasheet items fit well in the main view of the datasheet. For details, see DatasheetContent.

  • Mobile IT 1.2 features a server-side search for Mobile Packs. Until now only local search on a mobile device was available.

  • Support for customization and localization of strings describing various user interface elements in Mobile IT application is introduced in Mobile IT 1.2. For more information, refer to the Customizing and Localizing UI Elements topic.

  • Since now Mobile Packs that do not require user authentication in Active Directory (that is, entering credentials) are supported. For instance, take a look at Quest Password Manager Mobile Pack. For more information, refer to the Creating Mobile Pack, Initiating User Re-Logon and Using Request Context Properties topics.

  • There is an ability to specify the default content type (alerts or reports) which should be displayed in Mobile Pack at start. For more information, refer to the section regarding manifest file description of the Creating Mobile Pack topic.

See Also


Was this topic helpful?

[Select Rating]



What's New in Mobile IT 1.1


Quest Mobile IT SDK Reference
What's New in Mobile IT 1.1
See Also 

Mobile IT 1.1 introduces a lot of new features and enhancements that allows creating custom Mobile Packs for target systems easily and efficiently. This section lists new features that are implemented in Mobile IT 1.1. Also it describes differences between Mobile IT versions 1.1 and 1.0.

What's New in Mobile IT 1.1

  • Support for Mobile Pack instances — From now on each Mobile Pack can have one or more instances associated with the different hosts.

  • Ability to configure instance parameters — Each instance of Mobile Pack can be individually configured. For more information, refer to the Using Package Parameters topic.

  • Granular alerting — Alerts can now be sent to specific users or groups of users. For more information, refer to the Sending Simple Alert topic.

What's Different from Mobile IT 1.0

  • Unlike version 1.0 in version 1.1 multiple Mobile IT Agents may work with a single Mobile IT Server.

  • In version 1.1 Mobile Packs are presented by .mobilepack files with a completely redesigned format. To start using Mobile Pack, its corresponding .mobilepack file should be uploaded to Mobile IT Server through Mobile IT Administrative Console. For more information, refer to the Creating Mobile Pack and Working with PowerPacks topics.

  • The IPlugin interface is now replaced by the IAlertProvider and IReportProvider interfaces.

  • Now Mobile IT Server is able to monitor statuses of Mobile Pack instances through the IStatusProvider interface.

  • REST API is not available to use at this moment. An updated version of REST API is going to be introduced in future releases of Mobile IT.

See Also


Was this topic helpful?

[Select Rating]



Service
Consulting Services
Educational Services
Support Services
Related Documents