My user’s issue was that he was not having access to read “Process” at the organization level. I had previously set it up to “User” level. After changing the access level as follows, he was able to qualify leads without any issues.
Most important thing here is that when you query your ObjectTypeCode and corresponding Object Name for code 4703, it will return the name as WorkFlow. Note that on Security Role setup, it’s nothing but Process.
I have a requirement in which I have to access a SQL view from within my customisation dictionary, in order to create a custom lookup for users to select a value based on an Extender form and an Extender lookup. Easiest option is to create an Extender view (which in turn creates a SQL view for us).
Now, this is the view that I am suppose to refer to from my custom dictionary. Dexterity allows us to refer to any SQL object by simply create a TABLE definition and mention the SQL object (table or view) name as the physical name.
Everything looks perfect till you actually see below error messages at runtime:
Error message is quite obvious; you do not have DEX_ROW_ID in that SQL view that you are referring to. Every single Dexterity table must have DEX_ROW_ID at the backend. It cannot afford to not have one.
So how am I going to resolve this? By simply adding a record number dynamically to the SQL view created by Extender. How to do that? By adding the T-SQL function ROW_NUMBER(). This is how I achieved it:
Whenever I accidentally press the power button on my MacBook, it switches off the display. This behaviour change happened from OS X Mavericks (10.9).
Earlier it used to let us choose with following options:
OSXDaily.com has got a workaround for this trouble. It does not straightaway enable these options the moment you press the power button, but it prevents OS X Mavericks from switching the display off, which is far more relieving.
To invoke the above power button options: press power button continuously for a second or two.
This post is so very different, even if it’s an off-topic one, from what I usually post on my blog. But considering the fact that I have been witnessing some of the worst things that directly relates to this topic, I think it’s quite timely.
To just brief you on this, an employee can get motivated in a typical corporate environment to perform well: to get promoted and climb up the corporate ladder OR to play it safe and prevent undesired. Both have it’s own pros and cons.
In my opinion, at times, promotion oriented motivation could easily lead one to become power-hungry and become selfish in achieving his/her goals that are totally self-centred. It easily poisons one’s attitude to put his/her organisation’s goals down. If this person is at middle level in an organisation hierarchy to whom people report, it could get worser than you might imagine. He/she becomes the biggest threat to an organisation than even the organisation’s competitors. I have witnessed this big time in the very recent past. So that makes this topic so relevant to me personally.
In a stark contrast, prevention oriented motivation could easily lead one to become completely oblivious unless his/her contribution is duly noticed by management and reward him/her without wasting any time. This person becomes oblivious when management fails to notice and recognise. Also, this approach may quite easily make the management to believe that such person would work and contribute irrespective of whether he/she is recognised and rewarded or not.
While promotion oriented approach may backfire at an organisation’s health, prevention oriented approach may backfire at the individual’s career and growth.
Big question hanging in front of me: How To Strike A Balance Between Both?
Do not hesitate to share your thoughts in the comments section.
An interesting post that I read on Ventana Research by Robert Kugel.
Originally posted on :
In the wake of the past year’s usual crop of failed ERP implementations, I’ve read a couple of blogs that bemoan the fact that ERP systems are not nearly as user-friendly or intuitive as the mobile apps that everyone loves. I’ve complained about this aspect of ERP, and our research confirms that ERP systems are viewed as cumbersome: Just one in five companies (21%) said it is easy to make changes to ERP systems while one-third (33%) said making changes is difficult or very difficult. Yet as with many such technology topics, addressing the difficulty in working with ERP systems is not as straightforward as one might hope. ERP software vendors must make it easier, less expensive and less risky for customers to adapt the systems they buy to their changing business needs. To do this, vendors must design products to be more configurable. The goal should be that…
One of my users use Mac OS X Mavericks and his major concern was to batch print files in a folder without opening each one of them. He somehow (?!?!?!) trusted my expertise in Mac OS to find a solution.
My best friend, Google, came to my rescue again. I got this gem of a post by Jesse Chapman (sorry Jesse, I tried getting a profile page of yours, but could only get your twitter page) on his blog wait, really? that saved my day.