Abstract: A method and system for validating translated files for inclusion in an application being developed. Translatable files having externalized content in a single base language are sent for translation into other languages. Translated files resulting from a translation of the translatable files are received. Each translated file is statically and dynamically validated to detect error(s). The static validation is based on comparing the translatable files to the translated files. The dynamic validation is based on a simulation of how a user interface of the application presents the externalized content, without including an actual presentation of the externalized content by the user interface. Modified translated files that correct the detected error(s) are received and provided for a presentation of the externalized content by the user interface.

Abstract: File selection techniques that can handle overlapping module contexts provide flexible and reversible backup, restore, migration, deployment and synchronization operations. Both remote (administrative) control and local (user) control of the file selection are provided. Application and configuration specific templates are provided to a user from the remote administrator for further customization by selecting or de-selecting configurations, applications and/or individual files or configuration entries. The templates may be controlled geographically by the IP address or identity associated with the user. A user's interaction with the customization is saved and the order of changes is maintained, so that when the templates are updated, the user's customizations can be re-applied. The administrator may override user settings based on rules, which may also be geographically determined. The file selection may also be altered based on media type and location, e.g., local backup vs. server backup.

Abstract: Embodiments of the invention provide for authenticating users of web-based applications by presenting a previously acquired signed digital signature. Examples establish secure user sessions between a client and a user in response to a verification of an identification of the user by the client, the client creating a unique username for the user and unlocking access by the user to a client digital signature for use with a request for service from a third party web server. A secure facilitator session is established between the client and a third party web server, wherein messages exchanged with the unique username and a unique session identification indicia of the secure facilitator session signed by the unlocked digital signature result in executed processes requested by the service identifier data if the messages are validated without the client requiring the user to verify user identification for any message until a secure facilitator session ends.

Abstract: A modification method and system. The method includes retrieving by a computer processor of a computing system a list of features and plug-ins associated with an application. The features include features version metadata and the plug-ins include plug-ins version metadata. The computer processor compares features source code associated with the features with previous versions of associated source code. The computer processor generates modified features version metadata associated with the features version metadata. The modified features version metadata includes updated version labels differing from previous version labels of the previous versions of associated source code. The features are assembled into an application.

Abstract: A modification method and system. The method includes retrieving by a computer processor of a computing system a list of features and plug-ins associated with an application. The features include features version metadata and the plug-ins include plug-ins version metadata. The computer processor compares features source code associated with the features with previous versions of associated source code. The computer processor generates modified features version metadata associated with the features version metadata. The modified features version metadata includes updated version labels differing from previous version labels of the previous versions of associated source code. The features are assembled into an application.

Abstract: Embodiments of the present invention provide an approach to automatically convert existing support materials (support manuals, troubleshooting guides, content, help files, etc.) into machine-executable programs so as to obviate for manual execution of the steps described in the support materials. That is, the embodiments of the invention will (among other things): create support-based programs that automate the execution of previously manual steps; create an inventory of said programs; parse existing support documentation; map sections of each support document into existing program automation; construct a sequence of program automations that resemble the flow of each support document; and/or associate a constructed sequence of automation with a support document that could be executed automatically.

Abstract: Embodiments of the invention provide for authenticating users of web-based applications by presenting a previously acquired signed digital signature. Examples establish secure user sessions between a client and a user in response to a verification of an identification of the user by the client, the client creating a unique username for the user and unlocking access by the user to a client digital signature for use with a request for service from a third party web server. A secure facilitator session is established between the client and a third party web server, wherein messages exchanged with the unique username and a unique session identification indicia of the secure facilitator session signed by the unlocked digital signature result in executed processes requested by the service identifier data if the messages are validated without the client requiring the user to verify user identification for any message until a secure facilitator session ends.

Abstract: A method and system for validating translated files for inclusion in an application being developed. Translatable files having externalized content in a single base language are sent for translation into other languages. Translated files resulting from a translation of the translatable files are received. Each translated file is statically and dynamically validated to detect error(s). The static validation is based on comparing the translatable files to the translated files. The dynamic validation is based on a simulation of how a user interface of the application presents the externalized content, without including an actual presentation of the externalized content by the user interface. Modified translated files that correct the detected error(s) are received and provided for a presentation of the externalized content by the user interface.

Abstract: A modification method and system. The method includes retrieving by a computer processor of a computing system a list of features and plug-ins associated with an application. The features include features version metadata and the plug-ins include plug-ins version metadata. The computer processor compares features source code associated with the features with previous versions of associated source code. The computer processor generates modified features version metadata associated with the features version metadata. The modified features version metadata includes updated version labels differing from previous version labels of the previous versions of associated source code. The features are assembled into an application.

Abstract: File selection techniques that can handle overlapping module contexts provide flexible and reversible backup, restore, migration, deployment and synchronization operations. Both remote (administrative) control and local (user) control of the file selection are provided. Application and configuration specific templates are provided to a user from the remote administrator for further customization by selecting or de-selecting configurations, applications and/or individual files or configuration entries. The templates may be controlled geographically by the IP address or identity associated with the user. A user's interaction with the customization is saved and the order of changes is maintained, so that when the templates are updated, the user's customizations can be re-applied. The administrator may override user settings based on rules, which may also be geographically determined. The file selection may also be altered based on media type and location, e.g., local backup vs. server backup.