Best Practice for module components based on API's

Hi all,
is there a white paper/other documents which outline best
practice for using table/module component api's and best
approaches to get around restrictions?
I would also appreciate war stories about using this method of
Forms development bearing in mind i would be using this as the
foundation of a web deployed based application (intranet first -
ultimately internet).
Thanks
Mark
null

You cannot add agents to skills dynamically; however, you can queue the caller into more than one CSQ based on statistics. You would use the Get Reporting Statistics and an If step within the Queued branch of your first Select Resource step. If the condition is met (e.g. Contacts Waiting >= 10) then exectue a second Select Resource step within the queued branch of the first. The contact would then be waiting in both CSQs waiting for an agent.

Similar Messages

Best practices for setting environment based static variables?

I have a set of static string variables that hold the url location of modules in a project. These locations change depending on whether I'm building for development, staging or production.
What's the best way to set static variables in this way?

I don't know if this is best practice, but here's the solution I've come up with.
The root domain is accessible within the swf via a node on a loaded xml file. So I created a simple method that sets a url variable based on that domain node.
The domain-based url variable is then used within the static string variables that define the location of the modules.
Simplified like so:
var domain:String = xml.node.value;
static var bucketLocation:String = getLocation()
static var moduleLocation:String = bucketLocation + "modulename.swf";
function getLocation():String
     var loc:String
     switch (domain) {
          case stagingUrl:
              loc = "pathToAmazonStagingBucket";
               break;
          case productionUrl:
               loc = "pathToAmazonProductionBucket";
               break;

Best practices for adding components in a composite custom component

Hello,
I am developing a custom, composite JSF component need to dynamically add child components in my renderer class. I've noticed that people add components to a custom component in many different ways. I'd like to follow JSF best practices when developing this component - of the following approaches, which would you recommend? Or is there yet another approach I should be using?
1) in the encodeBegin method of my renderer class, create a new component, add it to the component tree, and let the page life cycle take care of the rendering:
HtmlDataList dimensionStateGroupDataList = (HtmlDataList) app.createComponent( HtmlDataList.COMPONENT_TYPE );
//set properties on dimensionStateGroupDataList
component.getChildren().add(dimensionStateGroupDataList);
2) in either the encodeBegin or encodeEnd method, create a component and encode it:
HtmlDataList dimensionStateGroupDataList = (HtmlDataList) app.createComponent( HtmlDataList.COMPONENT_TYPE );
//set properties on dimensionStateGroupDataList
dimensionStateGroupDataList.encodeBegin();
dimensionStateGroupDataList.encodeEnd();
Both of these methods are functional, and I prefer the first (why encode children if you don't have to?), but I am interested in other people's take on how this should be done.
Thanks for your help.
-Christopher

My bad, sorry, wasnt concentrating, Im afraid I have no experience with portlets, but I would have thought that you can mimic the outputLinkEx in you renderer by encoding your own links?
If you were to bind a backing bean variable to an outputLinkEx what would it be? Not understanding portlets, or knowing what an outputLinkEx is may be hindering me, but you should be able to create an instance of it in code like (this example uses HtmlOutputLink, you would need to know which component to use):
HtmlOutputLink hol = new HtmlOutputLink();
hol.set....Then set any attributes on it, and explicitly call its encodeStart, encodeEnd functions. Is that way off the mark.

Best practice for adding agents based on queue stats

I am looking for some guidance (sanity check really) on the best way for to add agent to a CSQ base on call statistics. Scenario: 20 agents logged in and ready. The first 15 agents take all the calls until the contacts waiting reaches 10, then and only then should the other 5 agents start taking calls.
I appreciate any help or sample scipts on this subject.

You cannot add agents to skills dynamically; however, you can queue the caller into more than one CSQ based on statistics. You would use the Get Reporting Statistics and an If step within the Queued branch of your first Select Resource step. If the condition is met (e.g. Contacts Waiting >= 10) then exectue a second Select Resource step within the queued branch of the first. The contact would then be waiting in both CSQs waiting for an agent.

View State Best Practice for Hiding Components?

When changing states and hiding components, what is the best practice?
Set Height/Width=0?
Set Visible/IncludeInLayout=False?
Or is there a better way?

Good point. That's what I thought but I'm working through 'Adobe Flex 3 Training from the Source' and they explicitly set width/height to 0 in the new state so I thought I was not doing it correctly.

Best practices for complex recipe-based system?

Hi Folks,
I'm at about the intermediate level (working on my CLD), and tasked with re-vamping a tighly-developed control system(which I'm intimately familiar with) into more of a configurable 'recipe'-based system. Basically the current front-end control software does a lot of the work for the end user - it pre-defines flows, assumes certain electrical/plumbing configurations, etc. This is fine for the 'production floor', however the R&D guys would like something a bit more configurable.
This system comprises of several flow controllers, mostly controlled/monitored via analog I/O (compact FieldPoint). There's some static analog input channels devoted to temp, humidity, etc. There exists the possibility of 1-2 external RS232 metering devices as well.
Anyway I'm trying to work out the foundation for the UI. In terms of architecture think a que-ed state machine is my best bet due to the number of parallel processes occuring at once (analog acq, multiple serial comm, TDMS, UI, etc). Basically I'd like the user to be able to add/remove/modify 'steps'. For instance, "Set Flow: controller IDx, 20cfm", or "Time Delay, Static: 10:00", "Time Delay, Psuedo-Static, based on X".
I've worked out a configuration UI (utilizing the in-build NI configuration storage VIs) to associate the analog channels to external devices (ie Aout1="Controller1 SP", Ain1="Controller1 FB"). Later I'll populate a ring control, for instance, for the 'add SetFlow step', to list all of the analog OUTs for selection.
So I guess what I'm looking for is advice on passing all this info around without having to re-hash it all the time to present to the user. Keeping in enum/ring allows for easy user viewing, changing, and block diagram readbility (vs string constants, which are error prone) - is this something that the 'flatten to string' would be helpful for (something I have no experiance using).
What tips can you provide for moderate-complexity HMI control systems developed strictly in LV? We currently don't have DSC, and I'm a bit closed-minded about using it for this (but perhaps you can convince me otherwise?).
Thanks for your time,
Jamie
Message Edited by 8bitbanger on 04-21-2010 08:10 AM
v2009 devel. w/RT

Cool, thanks for the screenshot!
This request for more customization was anticipated, so I began working things in last year with other minor revs. The first was this 'hardware configuration' utility. Right now I'm only using the MFC Config page for channel scalling/name info. (the production version still relies on 'static' channel associations to control devices). The enum 'card/slot' selector does exactly as you mentioned - it controls a tab value, which loads other pages (with similar info).
The second 'generator' page is used to populate a list of generators available for the user to select, and works quite well - users can add somewhat custom generators to the list w/out having to specify "custom" every time (and I don't have to rebuild to add such a simple thing).
You can see the 'Flow Control' and 'Monitor' channel that have not yet been implimented. :-)
Lastly the mockup is where I want to end up. I *wish* that labview was able to incorperate enum/ring drop-downs within a table cell (without the hacks that I've seen suggested).
I intended to setup a similar format for the 'steps' - an Action (or noun as you say), Target (ie file path, device name, etc), Value (setpoint, other pertinent data), etc. Do you pass this info around as a cluster in your VI then simply parse out to the UI in the steps listing? My hurdle is how to ellegantly relate, say, a CSV file back to the enums without a lot of hard-coded (constant) strings.
Cheers,
Jamie
::edit:: *Finally* found the button to insert images... ::edit::
Message Edited by 8bitbanger on 04-21-2010 10:30 AM
v2009 devel. w/RT
Attachments:
config_UI.JPG ‏52 KB
generators.JPG ‏39 KB
mock-up.JPG ‏33 KB

Best practice for deleting data based on mismatch

I have two tables which share the same key columns (one is an extension table of the other, basically)
INVPARTINSTOCK_C is current data
INVPARTINSTOCK_D is a date extension table
I want to remove all data in D which is not in C
I can gather a list of mismatched data by using:
select
d.Contract,
d.Part_No,
d.Location_No,
d.Lot_Batch_No,
d.Serial_No,
d.Eng_Chg_Level
from invpartinstock_d d
MINUS
select
c.Contract,
c.Part_No,
c.Location_No,
c.Lot_Batch_No,
c.Serial_No,
c.Eng_Chg_Level
from invpartinstock_c c but how do I apply that to a DELETE FROM INVPARTINSTOCK_D WHERE... ?
Thanks

1) It depends on, at least, the data volumes we're talking about, but
DELETE FROM dtable
WHERE (column_list) IN (your_minus_query)should be functionally correct. Probably more efficient would be
DELETE FROM invpartinstock_d d
WHERE NOT EXISTS(
    SELECT 1
      FROM invpartinstock_c c
     WHERE c.contract = d.contract
    )2) Why isn't there a foreign key relationship that prevents this sort of mismatch in the first place?
Justin

Best Practices for AP Power

Can someone tell me or explain to me if there are best practices for AP Power based on data or voice networks? Specifically, if you're tasked to do a Wireless Site Survey with the intention that RRM will not be used how would you configure the APs power for data usage only or voice and data.
I have never read anything that states a best practice for power ... I tend to set APs at 6 or 12 mW for 2.4GHz and 12mW or 25mW for 5GHz ... but there isn't anything to state whether my practice meet any type of best practice so I'm just looking for any supporting facts or idea of what other Wireless Engineers use when they do site surveys.
Any information or shared thoughts are much appreciated!!!
Thanks,
Mal

Hello Mal,
Your question will cause a number of responses from the different RF chefs here, Im sure!
Ive been in WiFi for a long time. When I sit down with educated customers they will ask the same question. Based on my experience designing high availability, data intensive networks I follow the practice to design for the "lowest" common denominator.
With this being said, its often a 5 GHz Phone device or even a 2.4 GHz Vocera badge. In any case, both devices live in or around 20mW. I like to design my networks at 12.5mW. I find this works better for RRM and also builds in fluff incase I need to adjust power on a AP.
If a customer requires both a 2.4GHz and 5 GHz design. I will just design 5 GHz @ 12.5 mW, as the 2.4 GHz network will surly fit inside of the 5 GHz design.
I hope this helps...

"Best practice" for components calling components on different panels.

I'm very new to Swing. I have been learning from tutorials, but these are always relatively simple interfaces , in which every component and container is initialised and added in the constructor of a main JFrame (extension) object.
I would assume that more complex, real-world examples would have JPanels initialise themselves. For example, I am working on a project in which the JFrame holds multiple JPanels. One of these Panels holds a group of JToggleButtons (grouped in a ButtonGroup). The action event for each button involves calling the repaint method of one of the other Panels.
Obviously, if you initialise everything in the JFrame, you can simply have the ActionListener refer to the other JPanel directly, by making the ActionListener a nested class within the JFrame class. However, I would like the JPanels to initialise their own components, including setting the button actions, by using an extension of class JPanel which includes the ActionListeners as nested classes. Therefore the ActionListener has no direct access to JPanel it needs to repaint.
What, then, is considered "best practice" for allowing these components to interact (not simply in this situation, but more generally)? Should I pass a reference to the JPanel that needs to be repainted to the JPanel that contains the ActionListeners? Should I notify the main JFrame that the Action event has fired, and then have that call "repaint"? Or is there a more common or more correct way of doing this?
Similarly, one of the JPanels needs to use a field belonging to the JFrame that holds it. Should I pass a reference to this object to the JPanel, or should I have the JPanel use "getParent()", or some other method?
I realise there are no concrete answers to this query, but I am wondering whether there are accepted practices for achieving this. My instinct is to simply pass a JPanel reference to the JPanel that needs to call repaint, but I am unsure how extensible this would be, how tightly coupled these classes would become.
Any advice anybody could give me would be much appreciated. Sorry the question is so long-winded. :)

Hello,
nice to get feedback.
I've been looking at a few resources on this issue from my last post. In my application I have been using the Observer and Observable classes to implement the MVC pattern suggested by T.PD.(...)
Two issues (not fatal, but annoying) with this are:
-Observable is a class, not an interface; since most of my Observers already extend JPanel (or some such), I have had to create inner classes.
-If an Observer is observing multiple Observables, it will have to determine which Observer called its update() method (by using reference equality or class comparison or whatever). Again, a very minor issue, but something to keep in mind.I don't deem those issues are minor. The second one in particular, is rather annoying in terms of maintenance ("Err, remind me, which widget is calling this "update()" method?").
In addition to that, the Observable/Observer are legacy non-generified classes, that incurr a loosely-typed approach (the subject and context arguments to the update(Observable subject, Object context) methods give hardly any info in themselves, and they generally have to be cast to provide app-specific information.
Note that the "notification model" from AWT and Swing widgets is not Observer-Observable, but merely EventListener . Although we can only guess what reasons made them develop a specific notification model, I deem this essentially stems from those reasons.
The contrasting appraoches are discussed in this article from Bill Venners: The Event Generator Idiom (http://www.artima.com/designtechniques/eventgenP.html).
N.B.: this article is from a previous-millenary series of "Design Techniques" articles that I found very useful when I learned OO design (GUI or not).
One last nail against the Observer/Observable model: these are general classes that can be used regardless of the context (GUI/non-GUI code), so this makes it easier to forget about Swing threading rules when using them (essentially: is the update method called in the EDT or not).
If anybody has any information on the performance or efficiency of using Observable/ObserverI would be very surprised if this had any performance impact. If it had, that would mean that you have either:
- a lot of widgets that are listening to one another (and then the Mediator pattern is almost a must to structure such entangled dependencies). And even then I don't think there could be any impact below a few thousands widgets.
- expensive or long-running computation in the update methods. That's unrelated to the notification model itself.
- a lot of non-GUI components that use the Observer/Observable to communicate among themselves - all the more risk then, to have a GUI update() called outside the EDT, see remark above.
(or whether there are inbuilt equivalents for Swing components)See discussion above.
As far as your remark 2 goes (if one observer observes more than one subjects, the update() method contains branching logic) : this also occurs with the Event Delegation model indeed: for example, it is quite common that people complain that their actionPerformed() method becomes unwieldy when the same class listens for several JButtons.
The usual advice for this is, use anonymous listeners, each of which handles the event from only one source (and generally very close in code to the definition of that source), and that simply translates the "generic" event notification method into a specific method call of a Controller or Mediator .
Best regards.
J.
Edited by: jduprez on May 9, 2011 10:10 AM

Best practice for placing module

Hello
I have an enterprise application project, with :
1) EJB Module
2) Web Module .
I want to add the hibernate jars+classes+data+servlets+utils etc...
Should i create a new Web module for hibernate or should i add it to the existing EJB module which is my business logic ?
What is the best practice for that?
Thanks !

Thanks for the reply, Jiri.
I believe that the answer is 'yes' to both of your questions above. I do have a question about the formatting of the meta tag itself, as my main question is how do I extract the needed information from a particular CDF so that it is displayed in the <head> section located in the page template.
I have a Region Definition for the content section of my page with a 'Title' field, which a contributor can fill in, save, and create a Contributor Data File with their own specified title. Let's also say that my page template, which formats the entire page, looks like this (rough):
<html>
<head>
<title>Web page</title>
</head>
<body>



</body>
</html>
What would my <meta> tag look like for the following:
<meta property="og:title" content="Title of the content section"/>
Let's name our templates/definitions:
Page Template: PT_META
Region Template: RT_META
Region Definition: RD_META
Contributor Data File: CDF_META
In other words, how do I extract the information included in the Contributor Data File (as well as its metadata) for use in the Page Template? Is there some sort of Idoc Script call that can be used?
Thank you so much,
Josh

Highly Required CRM 5.0 Best practices for CRM Service Module

Dear all,
I have been searching for CRM 5.0 version best practices in Internet quiete a long period, but could not find anywhere.
currently SAP is providing only best practices for SAP CRM 2007 version.
since most of configuration is differing because of Webclient Interface, I request you to refer a source from where I can get the CRM 5.0 Best Practices for Service module.
Your suggestions and help will be highly appreciated.
Best regards
Raghu ram

Hi Srini,
<removed by moderator>
Thank you & Best regards
Raghu ram
Edited by: Raghu Ram on Jul 16, 2009 6:09 AM
Edited by: Raghu Ram on Jul 16, 2009 6:11 AM
Moderator message please review the rules of engagement located here:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/home/rulesofEngagement
Edited by: Stephen Johannes on Jul 16, 2009 8:12 AM

Best practices for Refreshing Unv Structure for SAP based universes

This may sound basic and I apologize for asking this, but the refresh structure in SAP based universes is somewhat different from noraml universes.
Here is what i'd like to do:
- Hide all the L00 objects.
- Rename all the L01 objects and move them to a new Class.
- Change some of the detail (attribute) objects to dimension objects.
- Hide the format and Unit for key figures.
- Hide all of the classes/subclasses that get automatically generated when a SAP based universe is created.
I have noticed that when I do the above and refresh the universe, it assumes that all these objects have gone missing from the original classes and adds them back to the universe.
I also want to make sure that if the select of an object gets updated and the object is re-named, then it should automatically pick up the change.
Lastly, I have some reports which were built prior to this renaming. I want to make sure that the reports do not break.
Thanks,
Kashif

Hi,
This thread is really old.
Yes it was a common problem back in the earlier XI 3.x days . a lot of bugs in this area were eliminated by the time of XI 3.1 SP03 FP3.x - you don't quote your version.
Actually, you need to be aware that a refresh structure is often not needed, and can corrupt the olap universe . Pls check out Note 1278216 - What are the best practices for OLAP Universe Change Management when using SAP Integration Kit?
in essence :
Only use 'Refresh Structure' functionality If:
- A new Object (Dimension/Characteristic) has been added to the BEx query (Rows/Columns/Free Characteristics)
- A new Variable Restriction has been added to the Bex query Filters
Do not use 'Refresh Structure' functionality after:
- Having modified a STRUCTURE in BEx. i.e. 'Detail view of Formula' or 'Details of Selection', or changing the General Description of structure members.
- Doing manual actions on objects/classes in the OLAP Universe like: Move ; Cut/Paste ; Drag/Drop ; Hide ; Delete.
(because these workflow can lead to corruption)
regards,
H

Best Practice for PDF print forms based on SAP standard

Hi,
I have copied the SAP standard PDF form F_D_INT_SCALE_00 to a Z form, and am using it in conjunction with the standard print program RFDZIS01_PDF. However I need to output some additional fields that are not supplied by the print program / interface (for example Customer VAT number).
What is the best practice for achieving this? As far as I can see the only way is to take a copy of the standard print program and modify it to select the extra data, and modify the interface. I never like taking copies of standard programs though for obvious reasons.
If I had this requirement with a smartform it would be a simple case of embedding ABAP code into the Z smartform and leaving the print program alone, but unfortunately there is no provision for the non-PDF version of the Interest Letter to be sent by email.
Thanks in advance,
Vindaloo

Thanks for your reply Robert.
However I think you are referring to Smartforms when you mention Code Initialization and Global Data declarations. I need to know the best way to modify copies of standard Adobe Print Forms.
Regards,
Vindaloo

Best practices for setting up projects

We recently adopted using Captivate for our WBT modules.
As a former Flash and Director user, I can say it’s
fast and does some great things. Doesn’t play so nice with
others on different occasions, but I’m learning. This forum
has been a great source for search and read on specific topics.
I’m trying to understand best practices for using this
product. We’ve had some problems with file size and
incorporating audio and video into our projects. Fortunately, the
forum has helped a lot with that. What I haven’t found a lot
of information on is good or better ways to set up individual
files, use multiple files and publish projects. We’ve decided
to go the route of putting standalones on our Intranet. My gut says
yuck, but for our situation I have yet to find a better way.
My question for discussion, then is: what are some best
practices for setting up individual files, using multiple files and
publishing projects? Any references or input on this would be
appreciated.

Hi,
Here are some of my suggestions:
1) Set up a style guide for all your standard slides. Eg.
Title slide, Index slide, chapter slide, end slide, screen capture,
non-screen capture, quizzes etc. This makes life a lot easier.
2) Create your own buttons and captions. The standard ones
are pretty ordinary, and it's hard to get a slick looking style
happening with the standard captions. They are pretty easy to
create (search for add print button to learn how to create
buttons). There should instructions on how to customise captions
somewhere on this forum. Customising means that you can also use
words, symbols, colours unique to your organisation.
3) Google elearning providers. Most use captivate and will
allow you to open samples or temporarily view selected modules.
This will give you great insight on what not to do and some good
ideas on what works well.
4) Timings: Using the above research, I got others to
complete the sample modules to get a feel for timings. The results
were clear, 10 mins good, 15 mins okay, 20 mins kind of okay, 30
mins bad, bad, bad. It's truly better to have a learner complete
2-3 short modules in 30 mins than one big monster. The other
benefit is that shorter files equal smaller size.
5) Narration: It's best to narrate each slide individually
(particularly for screen capture slides). You are more likely to
get it right on the first take, it's easier to edit and you don't
have to re-record the whole thing if you need to update it in
future. To get a slicker effect, use at least two voices: one male,
one female and use slightly different accents.
6) Screen capture slides: If you are recording filling out
long window based databse pages where the compulsory fields are
marked (eg. with a red asterisk) - you don't need to show how to
fill out every field. It's much easier for the learner (and you) to
show how to fill out the first few fields, then fade the screen
capture out, fade the end of the form in with the instructions on
what to do next. This will reduce your file size. In one of my
forms, this meant the removal of about 18 slides!
7) Auto captions: they are verbose (eg. 'Click on Print
Button' instead of 'Click Print'; 'Select the Print Preview item'
instead of 'Select Print Preview'). You have to edit them.
8) PC training syntax: Buttons and hyperlinks should normally
be 'click'; selections from drop down boxes or file lists are
normally 'select': Captivate sometimes mixes them up. Instructions
should always be written in the correct order: eg. Good: Click
'File', Select 'Print Preview'; Bad: Select 'Print Preview' from
the 'File Menu'. Button names, hyperlinks, selections are normally
written in bold
9) Instruction syntax: should always be written in an active
voice: eg. 'Click Options to open the printer menu' instead of
'When the Options button is clicked on, the printer menu will open'
10) Break all modules into chapters. Frame each chapter with
a chapter slide. It's also a good idea to show the Index page
before each chapter slide with a progress indicator (I use an
animated arrow to flash next to the name of the next chapter), I
use a start button rather a 'next' button for the start of each
chapter. You should always have a module overview with the purpose
of the course and a summary slide which states what was covered and
they have complete the module.
11) Put a transparent click button somewhere on each slide.
Set the properties of the click box to take the learner back to the
start of the current chapter by pressing F2. This allows them to
jump back to the start of their chapter at any time. You can also
do a similar thing on the index pages which jumps them to another
chapter.
12) Recording video capture: best to do it at normal speed
and be concious of where your mouse is. Minimise your clicks. Most
people (until they start working with captivate) are sloppy with
their mouse and you end up with lots of unnecessarily slides that
you have to delete out. The speed will default to how you recorded
it and this will reduce the amount of time you spend on changing
timings.
13) Captions: My rule of thumb is minimum of 4 seconds - and
longer depending on the amount of words. Eg. Click 'Print Preview'
is 4 seconds, a paragraph is longer. If you creating knowledge
based modules, make the timing long (eg. 2-3 minutes) and put in a
next button so that the learner can click when they are ready.
Also, narration means the slides will normally be slightly longer.
14) Be creative: Capitvate is desk bound. There are some
learners that just don't respond no matter how interactive
Captivate can be. Incorporate non-captivate and desk free
activities. Eg. As part of our OHS module, there is an activity
where the learner has to print off the floor plan, and then wander
around the floor marking on th emap key items such as: fire exits;
first aid kit, broom and mop cupboard, stationary cupboard, etc.
Good luck!

What is the best practice for changing view states?

I have a component with two Pie Charts that display
percentages at two specific dates (think start and end values).
But, I have three views: Start Value only, End Value only, or show
Both. I am using a ToggleButtonBar to control the display. What is
the best practice for changing this kind of view state? Right now
(since this code was inherited), the view states are changed in an
ActionScript function which sets the visible and includeInLayout
properties on each Pie Chart based on the selectedIndex of the
ToggleButtonBar, but, this just doesn't seem like the best way to
do this - not very dynamic. I'd like to be able to change the state
based on the name of the selectedItem, in case the order of the
ToggleButtons changes, and since I am storing the name of the
selectedItem for future reference.
Would using States be better? If so, what would be the best
way to implement this?
Thanks.

I would stick with non-states, as I have always heard that
states are more for smaller components that need to change under
certain conditions, like a login screen that changes if the user
needs to register.
That said, if the UI of what you are dealing with is not
overly complex, and if it will not become overly complex, maybe
states is the way to go.
Looking at your code, I don't think you'll save much in terms
of lines of code.

Best Practice for module components based on API's

Similar Messages

Maybe you are looking for