Authentication is used by the server when it needs to know the identity of someone who is accessing their information.
Authorization is a process by which the server determines if the client has permission to use a resource or
access a file. In general, authentication answers the question“Who are you?” and authorization answers “What are you allowed to do?”.
In an earlier blog, we have discussed about Token based authentication and authorization and how it is being implemented in one of our projects. Over these past few months, we’ve made changes to our approach.
Read on to find out what enhancements we have made and why.
Tools used for implementation
We all might have gone through a situation at some point in Apple’s review process, where our app consistently gets rejected. You would have also thought that it is difficult to get approval for new apps. But it is very simple to get the approval if we abide by the review guidelines.
We have been in your shoes with the review process. With the experience we’ve gained over time on Apple’s review process, we’ve cracked the key to get an app reviewed and approved for listing in the Apple App Store. Compiled are the list of things you can do to reduce the review time, which have helped us immensely for the successful approval of our apps in a single go.
Good news is that Apple has reduced review process time. Usually the review time varies from app to app. On an average, 50% of the apps are reviewed in 24 hours and over 90% are reviewed in 48 hours.
“A shorter approval cycle” lets the developers to properly plan their app’s release.
Field level security in Microsoft Dynamics 365/CRM restricts access to the fields containing sensitive business data which are only accessible by authorized users.
It also serves as a means of adding an extra security around the field i.e Create, Update and Read value.
Dynamics Dev Helpmate – was developed as a bookmarklet for Microsoft Dynamics 365 developers. The idea behind this is to minimize the efforts and time in accomplishing the tasks related to customizations & navigations. This tool supports MS CRM 2013 and above versions.
FEATURES OF DYNAMICS DEV HELPMATE
Trigger action using JS
In many cases we may encounter a requirement where we are required to perform server side logic utilizing client side events (onchange, onsave, onload…etc) in MS CRM. We generally prefer to use actions for dealing with these kinds of operations.
So in this blog, we’ll take a detailed look at how to trigger an action and retrieve the action output parameters using script with a simple example.
Let us create a simple action which will trigger on save of the account and create a primary contact.
In this blog we’re going to look at the purpose of the schema migration tool provided by CakePHP and the benefits of using it in our project(s).
What does it do
Using a migration file we can create or drop tables, add or remove columns, create indexes and even insert data into our database. A migration file contains PHP script which handles our schema.
Most of the UI controls are usually provided by Apple while developing an app. Depending up on the requirements, it is common to change the default behavior and design of a UI control to create an app with uniform look and feel.
It is not only tedious but a bad practice to design/alter each control separately. Moreover, the process of altering each control not only time-consuming and cost-intensive but often prone to human error which could cause all sorts of compatibility problems with any other interdependent apps or systems.
QuickBooks SDK is a time tested option while doing custom programming against any flavor of QuickBooks Desktop edition. This SDK is based on COM with two interfaces: QBFC and QBXML.
QBFC uses pre-defined objects to build XML requests, whereas much of the plumbing has to be done by you with QBXML that includes XML serialization and deserialization.
While it is a breeze to consume the SDK from .NET based languages, the same is not true with other popular languages/frameworks such as PHP, Java, Node.js etc., because of the SDK’s roots in COM. Common problem across programming languages/frameworks is connecting to a remote instance of QuickBooks and perform pull/push of data.