Advantages and features of SAPCRM 2007

Hi ,
What are the Features and advantages of SAPCRM 2007 over previous versions particularly in Utilities industry .
We have a client presentation next week and we want to showcase them the new developments in CRM 2007 and how it will help to serve the customer better .
Please provide me links and related docs for this .
Thanks & RegardS,
Rahul D

Hi Rahul,
Main difference between the older CRM release to CRM 2007 is Web UI functionality for each scenario.
You can check the functional differences for each scenario of CRM in the below link.
https://websmp106.sap-ag.de/CRM
For features and benefits of CRM 2007, you may refer the below link.
http://www.sap.com/solutions/business-suite/crm/CRM_2007_features.epx
You may go through CRM configuration and best practices available in the below
link. (CRM 2007):
http://help.sap.com/bp_crmv12007/CRM_DE/BBLibrary/html/BBlibrary.htm
PCUI Cook book:
https://websmp203.sap-ag.de/~form/sapnet?_SCENARIO=01100035870000000202&_SHORTKEY=01100035870000647974&_OBJECT=011000358700001093962006E&
Hope this helps!!
Thanks and Regards,
Pavan Kumar Gali.

Similar Messages

  • Advantages and features of crystal report 13.0.2000.0

    Hi..
    i was using crystal report10.5 with visual studio 2008(c#)..
    recently we migrated to vs2010 and sap crystal reports..
    what are the advantages of sap crystal reports13.0.2000.0 when compare to crystal report10.5 ?...
    is there any new features added to sap crystal reports13.0.2000.0...

    Check the what's new article:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d01d0431-6928-2d10-1683-a2256fc6bd0d
    Cheers
    Fritz

  • What is the advantage and features of having a sky...

    what are the cost advantages of having a skype phone number and its features  ?
    Cheers Harvey

    Pro:
    By pre-compiling your JSPs you don't need a java compiler on the server - just a jre.
    The result? No java compiler on the server means a potential security hole patched - people can't just write and deploy jsp's willy nilly on the server.
    You KNOW that all your JSPs compile before you visit them - because you have compiled them all :-). It won't fail because of a stupid spelling miskate that prevents compilation. That doesn't mean they will run without error of course...
    Con:
    Compiling the JSPs ties them to a particular server - unless you take the runtime along with them.

  • Advantage and disadvantages of XI

    Dear All,
                 I was asked to list down the Advantages and Disadvantages of XI over other middleware tools in an interview
    Please advice.
    Regards,
    Ashish

    Hi Ashish,
    Advantages of XI:
    XI is a middleware like many others. It is well suited for connecting SAP systems with each other and with non-SAP.If your focus is not on SAP systems, other solutions might be a better choice today. SAP XI provides an integrated workflow engine that allows to define adapters to non-XML-protocols and mappings to convert data content from source to target.
    Any fully mature middleware should provide these three layers.
    1. An independent Message Queue
    2. A data consolidator and mapping engine
    3. Workflow processor.
    XI is lacking full-fledged Message Queue compared to other established Middleware products.
    Currently, SAP XI does not have the features like IBM Websphere, Seeburger or TIBCO.
    SAP's next XI release might provide this missing piece and many more features which is due 2007 i guess.
    Here are the advantages of SAP XI from my point of view.There are lots of advantages but to list a few :
    Easy Integration with SAP products & components (RFC, IDOC, Proxy).
    Data security as expected from any SAP product.
    Standards based - XML, XSD, Xpath etc
    Ability to communicate with other messaging systems/products.
    Business Process Management
    Synchronous & Asynchronous communication possible.
    Complex processes for communication possible instead of only sending and receiving (business process management) (connect e.g. asynchronous and synchronous steps, define complex communication scenarios)
    Mapping etc possible to accomplish in Java. Platform independent Java components.
    Java & .Net support.
    Big range of adapters for different technologies / tools (SOAP, Mail, JDBC, CDIX...)available in standard or offered by other companies (EDI e.g. by Seeburger).
    Process functionalities inside XI to modify content in the communication channel on own defined rules fpr business purposes.
    Central monitoring for data communication for all your communication between different systems.
    And the marketing issue: SAP and its partners provide high volume of development capabilities to make XI always up-to-date for new requirements
    Regards,
    Subhasha Ranjan

  • Troubleshooting and Introduction for Exchange 2007/2010 AutoDiscover - Details about "Test E-mail AutoConfiguration"

    AutoDiscover is a new feature in Exchange 2007, to provide access to Microsoft Exchange features (OAB, Availability service, UM) for Outlook 2007
    clients or later.
    We can determine whether problems related to AutoDiscover via OWA.
    For example:
    OOF is not working in Outlook Client but it is working in OWA.
    When we realized this issue is not related to Outlook Client side and network side after performing some troubleshooting steps, it should be something
    abnormal on AutoDiscover.
    There is a common tool to check AutoDiscover in Outlook, Test E-mail AutoConfiguration.
    Today, we will introduce AutoDisocver and “Test E-mail AutoConfiguration” in details. Hope it is helpful for AutoDiscover troubleshooting and self-learning.
    1. Differences between “Test E-mail AutoConfiguration” and other tools
    The “Test-OutlookWebServices” cmdlet allows us to test the functionality of the following services:
    Autodisocver
    Exchange Web Services
    Availability Service
    Offline Address Book
    When we run “Test-OutlookWebServices”, it returns all the web services’ states.
    However, some information are useless for some scenarios.
    For example:
    We just want our Exchange 2010 Server working internally. So it is unnecessary to enable Outlook Anywhere.
    However, when we run “Test-OutlookWebServices”, it returns Outlook Anywhere errors because the Outlook Anywhere does not need to been enabled.
    In contrast, using “Test E-mail Autodiscover” is more intuitive.
    If there is any problems, it will return error code from the test result, like 0x8004010F etc. We can do some research from TechNet articles or MS
    KBs.
    Although it is difficult to say where the specific problem is just via the error codes, we can combine with IIS logs to perform troubleshooting and
    find the root of problem.
    2. How to use “Test E-mail AutoConfiguration” Tool
    a. Open Outlook, we can find there is an Outlook Icon at the right bottom of System tray. Holding down “Ctrl” button and right click the Outlook Icon, we will see “Test E-mail
    AutoConfiguration” option. Please see Figure 01.
    Figure 01
    b. Click “Test E-mail AutoCofiguration” and input user name, uncheck the “Use Guessmart” and “Secure Guessmart Authentication” checkboxes, then click “Test”. Please see
    Figure 02.
    Figure 02
    c. “Test E-mail AutoConfiguration” result panel and log panel. Please see Figure 03 and Figure 04.
    Figure 03
    Figure 04
    3. How to understand “Test E-mail AutoConfiguration” result
    According to the Figure 03, we found there are many URLs in the “Test E-mail AutoConfiguration” result panel. Let us understand the details of these
    URLs.
    If we these URLs are not the correct ones, we can re-setting or re-creating them via commands.
    - Internal OWA URL:
    https://vamwan310.vamwan.com/owa/
    OWA internal access.
    - External OWA URL:
    https://mail.vamwan.com/owa/
    OWA external access.
    - Availability service URL:
    https://vamwan310.vamwan.com/EWS/Exchange.asmx
    Free/Busy, OOF and meeting suggestions.
    - OOF URL:
    https://vamwan310.vamwan.com/EWS/Exchange.asmx
    Out of Office access.
    - OAB URL:
    https://vamwan310.vamwan.com/OAB/023ef307-b18a-4911-a52c-de26700f6173/
    OAB access.
    - Exchange Control Panel URL:
    https://vamwan310.vamwan.com/ecp/
    ECP access.
    4. AutoDiscover Tips
    - AutoDiscover Service itself is a web application running on the AutoDiscover virtual directory (not a server service) designed to provide connection information to various
    clients.
    - The AutoDiscover service is automatically installed and configured when CAS role is added to any Exchange Server.
    - AutoDisocver virtual directory is created in IIS within the Default Web Site.
    - A Sercive-Connection-Point (SCP) object is created in AD.
    - The SCP contains a URL to the AutoDiscover service. This is for intranet clients so they do not have to use DNS to locate the AutoDiscover service.
    - In AD this object is located at the following location:
    DC=<domain>, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Administrative Groups, CN=Exchange Administrative
    Group, CN=Servers, CN=<CAS Name>, CN=Protocols, CN=AutoDiscover, CN=<CAS Name>
    - Setup creates the AutoDiscover URL based on the following structure:
    <CASNetbiosName>.domain.com/AutoDiscover/AutoDiscover.xml
    If a PKI certificate is not already present, a self-signed certificate is installed on the Default Web Site. 
    To help allow this certificate pass the Issues to test it is set up with a Subject Alternative Name containing urls.
    If a PKI certificate is present, that certificate is utilized and configured for use in IIS.
    The Outlook Provider is used to configure separate settings for the Exchange PRC protocol (internal to network), Outlook Anywhere (Exchange HTTP protocol), and WEB:
    EXCH, EXPR, WEB
    The
    EXCH and EXPR setting are vital for the proper configuration of Outlook.
    5. AutoDiscover Workflow
    General Process flow:
    There are various components surrounding the AutoDiscover Service and all are necessary to complete a request. Including IIS, AutoDiscover service
    itself, the provider, and AD.
    a.
    Client constructs service URL and submits Autodiscover Request. First attempt to locate the SCP object in AD. So, DNS is not needed.
    b.
    IIS Authenticates User.
    c.
    Is the Autodiscover service in the appropriate forest?
    + If YES.
        1)
    Parse/Validate Request
        2)
    Is there a provider that can service the Request?
    ++ If YES
          a)
    Config provider processes request and returns config settings.
          b)
    Return config setting to client
    ++ If NO
    Inform client we cannot process request
    + If NO.
    Redirect client to Autodiscover service in the appropriate forest.
    Methods to find Autodiscover services: SCP and DNS
    Domain-joined
    a. Find SCP first.
    The SCP contains the URL to the AutoDiscover service.
    URL: https://CAS01.contoso.com(CAS’ FQDN)/AutoDiscover/AutoDiscover.xml
    If more than one SCP object is found in AD (it means there are multiple CAS servers in the Exchange organization), Outlook client will choose one of the SCP entries that
    are in the same site to obtain the AutoDisocover URL.
    b. If we cannot find SCP object, then Outlook client will use DNS to locate AutoDiscover.
    Outlook parses out the domain (SMTP suffix) via your EmaiAddress, then attempts to connect to the predetermined order of URLs via the suffix.
    For example: If my email address is
    [email protected]
    Outlook tries POST commands to the following order of URLs:
    https://contoso.com/autodiscover/autodiscover.xml
    https://autodiscover.contoso.com/autodiscover/autodiscover.xml
    NOTE: The URLs above is by design, hardcode
    and cannot be changed.
    c.
    If those fail, Outlook tries a simple redirect to another URLs in IIS:
    http://contoso.com/autodiscover/autodiscover.xml
    http://autodiscover.contoso.com/autodiscover/autodiscover.xml
    If none of these URLs work then DNS is most likely not set up correctly.
    We can test that by pinging one of the above URLs.
    If that is successful, we must ensure the URLs contoso.com or autodiscover.contoso.com are actually pointing to the CAS server.
    If the ping fails then there is a chance that DNS is not set up correctly so be sure to check that the URLs are even registered.
    NOTE: If contoso.com is a non-CAS server,
    we should add a Host record with just AutoDiscover. And point that entry to your CAS server that is running AutoDiscover.
    d.
    If still failed, we can use DNS SRV lookup for _autodiscover._tcp.contoso.com, then “CAS01.contoso.com” returned. Outlook will ask permission from the user to continue
    with AutoDiscover to post to https://CAS01.contoso.com/autodiscover/autodiscover.xml
    Non-Domain-joined
    It first tries to locate the Autodiscover service by looking up the SCP object in AD. However the client is unable to contact AD, it tries to locate
    the Autodiscover service by using DNS.
    Then, same as step b, c, d in
    Domain-joined scenario.
    6. How to change the AutoDiscover
    service location order forcibly?
    By default, Outlook client locates AutoDiscover service in that order above.
    We can also change the order forcibly.
    a.
    If we want to locate AutoDiscover service via one of the autodiscover URLs, please running following command in EMS:
    Set-ClientAccessServer -identity <servername> -AutodiscoverServiceInternalUri https://autodiscover.contoso.com/autodiscover/autodiscover.xml(URL
    that you want)
    b. If we want to locate AutoDiscover service via
    SRV record, please follows this KB to set up SRV:
    http://support.microsoft.com/kb/940881
    7. How to check AutoDiscover Healthy
    a. We should make sure the AutoDiscover
    is healthy before using AutoDiscover to perform troubleshooting.
    b.
    We can browse following URL in IE explorer:
    https://autodiscover.vamwan.com/autodiscover/autodiscover.xml
    If it returns “code 600”, that means AutoDiscover is healthy.
    Screenshot as below:
    c. AutoDiscover itself returns errors to the requesting client if the incoming request does not contain the appropriate information to complete a
    request.
    The following table explains the possible errors that could be returned.
    Error   Value
    Description  
    600
    Mailbox not found and a   referral could not be generated.
    601
    Address supplied is not   a mailbox. The provided email address is not something a client can connect to.   It could
    be a group or public folder.
    602
    Active Directory error.
    603
    Others.
    The 600 “Invalid Request” error is returned because a user name was not passed to the service. That is OK for this test because this does confirm
    the service is running and accepting requests.
    d.
    If AutoDiscover service is not working well, I suggest re-building the AutoDiscover Virtual Directory for testing.
    Steps as below:
    1) Running following command in EMS to remove the AutoDiscover VD (we cannot delete it via EMC):
    Remove-AutodiscoverVirtualDirectory -Identity "CAS01\autodiscover(autodiscover.contoso.com)"
    Please refer:
    http://technet.microsoft.com/en-us/library/bb124113(v=exchg.141).aspx 
    2)
    Running following command in EMS to verify whether we have removed the AutoDisocver VD successfully:
    Get-AutodiscoverVirtualDirectory | FL
    Please refer:
    http://technet.microsoft.com/en-us/library/aa996819(v=exchg.141).aspx
    3)
    Running following command in EMS to re-creating a new AutoDiscover VD:
    New-AutodiscoverVirtualDirectory -Websitename <websitename> -BasicAuthentication:$true -WindowsAuthentication:$true
    Please refer:
    http://technet.microsoft.com/en-us/library/aa996418(v=exchg.141).aspx
    8. Common issues
    a. Outlook Disconnection
    Issue and Troubleshooting
    Issue:
    Sometimes the Outlook clients cannot connect to the Exchange server after migrating to a new Exchange server or changing to new CAS. The Outlook clients
    always connect to the old CAS server.
    Troubleshooting:
    To solve this issue, we should change the SCP via following command:
    Set-ClientAccessServer -Identity
    <var>CAS_Server_Name</var> -AutodiscoverServiceInternalUri
    https://mail.contoso.com(newCAS’FQDN)/autodiscover/autodiscover.xml
    b. Autodiscover
    Certificate issue
    Tips on Certificate:
    Exchange requires a certificate to run an SSL protocol such as HTTPS. We can use the certificate that supports subject alternate names (SAN) in Exchange.
    This is to allow the certificate to support resources that have different names, such as Outlook Anywhere and the Autodisocver Web application.
    Issue and Troubleshooting
    Issue:
    We receiver the Certificate Principal Mismatch error when we use a SAN certificate.
    Troubleshooting:
    1) Please determine the FQDN that the client
    uses to access the resource. Steps as below:
    OutlookàToolsàAccount
    SettingsàE-mailàclick
    the Exchange accountàChangeàMore
    SettingsàConnectionàExchange
    Proxy Settingsànote the FQND that list in the
    Only connect to proxy servers that have this principal name in their certificate box.
    2)
    Please using EMS to determine the value for the CerPrincipalName attribute: Get-OutlookProvider
    This command returns the result for the EXPR name.
    3)
    Please re-setting the CertPrincipalName attribute to match the FQDN via following command:
    Set-OutlookProvider EXPR –CertPrincipalName: “msstd:<FQDN the certificate is issued to>”
    9. Resource for reference:
    Autodiscover and Exchange 2007
    http://technet.microsoft.com/en-us/library/bb232838(v=exchg.80).aspx
    White Paper: Understanding the Exchange 2010 Autodiscover Service
    http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx
    Certificate Principal Mismatch
    http://technet.microsoft.com/en-us/library/aa998424(v=exchg.80).aspx
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    HI,
     I get following?  when run the test?  user is login to Domain A but accessing exchange in Domain B?

  • What is the significance of the Assembly Deployment Target and Feature Scope?

    Hello,
    We have created a project as Farm Solution (not sandbox).
    Under project properties we can see an option for Assembly Deployment Target : GAC or WebApplication.
    I know that GAC will deploy the dll to windows\assemblies and WebApplication will deploy to website/bin folder.
    Now, we add a feature to the project; in here we can see a dropdown for scope with options as: Farm; Web; Site; WebApplication. I know that depending upon what option is chosen; the feature can then be activated by going to the respective manage features
    option via SharePoint front end UI.
    Can you tell me what is the significance of the Assembly Deployment Target and Feature Scope?

    >>Can you tell me what is the significance of the Assembly Deployment Target and Feature Scope?
    Feature scope can be decided based on the type of artifacts you will be building
    Check the below link for what type of artifacts can be build at different levels of scopes
    http://msdn.microsoft.com/en-us/library/ms454835(v=office.14).aspx
     wrt to Assembly Deployment Target depends on what type of components you are deploying through your solution which will be specified in manifest.xml. There are advantages
    if you deploy the components to web application rather GAC like all Apppools will not get recycled, avoiding IIS reset etc. But if you have 3rd party dlls and feature receivers which need to deployed along with the solution then its advisable to deploy to
    GAC
    http://trentacular.com/2009/06/sharepoint-differences-between-global-and-web-application-targeted-solution-deployment/
    https://www.captechconsulting.com/blog/james-brocato/sharepoint-without-the-gac
    Hope this helps.
    My Blog- http://www.sharepoint-journey.com|
    If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

  • Advantages and Disadvantages of Dual booting Windows on PXI Device

     
    Hello,
    In solving my previous problem of running a DLL in RTOS I've stumbled upon another solution. But i wanted to know the pros and cons of this before i make the leap.
    I want to install windows on the PXI device so that the NHR DLL files are run inherently on the windows kernel and i have access over my DAQ devices without placing them in the remote target.
    What are the advantages and disadvantages of installing a windows only on the DAQ device and running all my operation from it. Do i loose my real time features? I dont know, I'm really new to LabView and may sound really dumb. Please excuse my lack of knowledge.
    With Regards,
    Khalid.

     
    Hello Bob,
    Thank you for your insightful answer. I also thought this might happen, loosing all the RT features.
    I have another question for you. If i use a RT variant of windows like "Windows Embedded 8", will this make any difference? Can i regain my RT features by it or i have to go with the LabView RTOS.
    I'm pushing towards a windows system because i have to run this DLL file from NHR which is not supported by the LabView RTOS.
    Moreover, I could just install just windows onto the PXI controller. I'm not being able to make it dual boot. Can you guide me towards proper guideline to do so? I looked at the knowledge base file about dual booting, but the instructions dont exactly match with my available options in BIOS setup.
    Any suggestions from anyone is much appreciated.
    With Regards,
    Khalid.
     

  • Should clients migrate right away to SOA Suite 12c?, what are the advantages and disadvantages?

    12c looks like a fine version, it seems to have a lot of advantages and new features. Is it recommendable for clients using 11g to make an effort and immediately adopt the new version of the suite?

    Hi there,
    I love the answer from my friend Chris here (+5 buddy!) You can't
    go wrong with this advice
    I just thought I would add that for any phones that can run both
    SCCP & SIP you find these comparison guides which may help;
    Feature Support by Protocol for the Cisco Unified IP Phone 8941 and 8945
    http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/8941_8945/8_5/english/admin_guide/6921apxg.html
    Cisco Unified IP Phone 6921, 6941, 6945, and 6961 Administration Guide  for Cisco Unified Communications Manager 9.0 (SCCP and SIP) - Feature Support by Protocol
    http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/6921_6941_6945_6961/9_0/english/admin_guide/P690_BK_4AB91FB_00_admin-6921-6941-6945-6961_appendix_01111.html
    Cheers!
    Rob
    "Why do the best things always disappear " 
    - The Band

  • Advantages and disadvantages

    What are the advantages and disadvantages of the MAC OS X v10.7 Lion??

    Positives.
    Newer native 64bit OS.
    Adds some features.
    Negatives.
    Need more system resources, More RAM, to run well.
    Flakey WiFi on some units not seen with earlier versions of OS X.

  • Advantages and disadvantages of SOAP adapter

    Hi all,
    Currently we need to provide a solution connecting to the .NET environment from SAP system, one of the option is proxy <-> PI <-> soap (web service), can anybody tell me the advantages and disadvantages of web service communication via PI? Because we may also be able to connect directly via the .NET connector.
    It will be very appreciated if you could provide some proposals, thanks.
    Bean

    Hi bean qian ,
    These are the advantages of SOAP:
    SOAP(Web Services) IS A Technical Adapter.
    Openness and Interoperability are features of SAP XI.
    1)Openness
    Use open, XML-based standards
    Leverage Industry Standards in B2B scenarios
    2)Interoperability
    Connect to applications using specialized adapters
    Connect to existing integration solutions using JMS (e.g. MQSeries) or SOAP
    Web Service: SOAP on the Ropes
    u2022 The Good
    u2022 By default the SAP builds the XML per the selected protocol
    u2022 All container elements with values are added to XML document
    u2022 SOAP protocol is a synchronous process, therefore SAP waits on a
    response
    u2022 SAP automatically matches data elements in the returned XML document to
    container elements and transfers the data (in theory)
    u2022 The Bad
    u2022 Current problems with return binding for SOAP processes require special
    handling
    u2022 The Web step allows manipulation of the outgoing and incoming XML
    document via rules
    u2022 the following may ease some learning pains
    These r disadvantages of SOAP :
    The SAP XI SOAP Adapter supports Exactly-Once end-to-end processing using unique message IDs.
    This is an excellent blog which neatly explains u in detail of SOAP with WEB:
    An Overview of SOAP

  • What are the advantage and disadvantages of upgrad...

    please do tell me the advantage and disadvantages of updating the software of my 5530. Thank you

    This is written generally as the specifics of the new 5530 update are unknown, although it is believed to be just a minor bug fix update.
    Advantages:
    Bug fixes
    Speed increases
    Stability increases
    The possibility of new features.
    Disadvantages:
    New bugs may be introduced.
    Something may go wrong during the update that could leave the phone unusable.
    Disappearing languages if the phone has previously been modified by the retailer (for example they imported the phone from another country and modified it to include other languages).
    If you are happy with your phone then it's probably best not to update it if you are worried about potential problems.

  • Advantage and Disadvantags of ActionScript 3

    Hi professionals of ActionScript 3!
    I just started flash animation and learning ActionScript. But
    I found one thing that there existing ActionScript 1, 2, 3 versions
    and ActionScript 2 components is using only ActionScript 2 code.
    Please tell me advantages and disadvantages of both ActionScript.
    Please advise which is powerful and has more info and sources. What
    kind of links between then existing.
    Thanks in advance!
    Said Babanli

    Said,
    > Please tell me advantages and disadvantages of both
    > [versions of] ActionScript. Please advise which is
    > powerful and has more info and sources.
    ActionScript 1.0 and 2.0 both run on the same virtual
    machine (AVM1)
    inside Flash Player. As of Flash Player 9, the player runtime
    features two
    virtual machines (AVM1 and AVM2), the second of which runs
    ActionScript 3.0.
    Right off the bat, this tells you that Flash Player 9 or
    higher is required
    if you want to program with ActionScript 3.0. In one sense,
    that's a
    potential "disadvantage" of AS3: if your users have Flash
    Player 8 or lower
    installed, you simply can't use that version of the language.
    Instead,
    you'll have to use AS2 (as far back as Flash Player 6) or AS1
    (as far back
    as Flash Player 5), or slash-notation proto-ActionScript if
    you need to go
    even further back than that. Ultimately, then, the version of
    ActionScript
    you use depends on the version of Flash Player you expect
    your users to have
    installed.
    AS2 is the first version of ActionScript to officially
    support custom
    classes (external text files structured in a particular way,
    using folders
    for classpaths and the "class" keyword). For more information
    on
    classpaths -- written for AS2, but basically applies to AS3
    -- see this URL:
    http://www.quip.net/blog/2006/flash/understanding-classpaths
    For many people (myself included), custom classes provide a
    powerful way
    to organize code into reusable objects -- just like the given
    objects in
    ActionScript's native API. Be aware, however, that custom
    classes are *not
    a required workflow* in AS2 or AS3. If you prefer, you may
    place your AS2
    or AS3 code into timeline keyframes, just like with AS1.
    Contrarily, even
    though true classes are not officially supported by AS1, you
    can mimic many
    of the benefits of classes by following the instructions here
    (an incomplete
    resource, but very useful):
    http://www.debreuil.com/docs/
    It would take pages and pages of notes to give you a
    thorough list of
    the benefits (and disadvantages!) of every version of
    ActionScript. Even
    then, it would be difficult to demonstrate that such a list
    was complete, so
    to keep things simple: as a general rule, each new version of
    ActionScript
    is presumed to be better than its predecessor. AS1 was more
    powerful than
    Flash 4-era ActionScript because it provided a considerably
    larger API. AS1
    also made it easier to target objects with dot notation than
    with slash
    notation and cumbersome getProperty() and setProperty()
    functions. AS2 was
    more powerful than AS1 because it provided native support for
    classes. It
    introduced variable typing, which helped with code completion
    and
    compile-time error checking. (AS2 also coincided with an even
    larger API,
    but that's a parallel benefit due to increased functionality
    in subsequent
    versions of Flash Player.) AS3 is more powerful than AS2
    because the syntax
    of custom classes has become more strict. I personally find
    that stricter
    syntax helps a programmer avoid "lazy" or "sloppy" practices,
    encouraging
    the programmer to code with purpose.
    For more thoughts along these lines, here's a free excerpt
    from a book I
    recently co-authored for O'Reilly (bear in mind, these are
    largely
    subjective opinions, but they work for me):
    http://www.communitymx.com/abstract.cfm?cid=16D76
    I'll probably start repeating myself soon, but to sum up:
    AS2 has
    advantages over previous versions because it provides
    numerous options and
    improvement in ease of use. AS3 improves even further by
    "cleaning up" the
    language by making it more strict and by providing a stronger
    internal
    consistency.
    Here are a few quick examples.
    In AS2, to create an instance of the Sound class (that is,
    an object you
    can use for programming audio), you simply use the "new"
    keyword:
    // AS2
    var mySound:Sound = new Sound();
    Most classes can be instantiated in this way, but in AS2,
    there are
    notable exceptions, including movie clips and text fields.
    // AS2 -- this does NOT work!
    var myMC:MovieClip = new MovieClip();
    var myTF:TextField = new TextField();
    This can be confusing to a newcomer, because it seems so
    arbitrary.
    (Someone new might well think, "Why can't instances be made
    the same way
    across the board?") In AS3, instantiation is more consistent:
    // AS3
    var mySound:Sound = new Sound();
    var myMC:MovieClip = new MovieClip();
    var myTF:TextField = new TextField();
    This is also true for event handling. In AS2, there are four
    or five
    ways to do it: the on() and onClipEvent() functions, their
    dot notation
    equivalents, addListener(), and addEventListener(). They're
    all valid in
    AS2, but not all interchangeable. Some work for components,
    some for other
    sorts of objects. It takes effort to memorize which objects
    work with which
    approach. In AS3, outside of a very small number of
    exceptions, most event
    handling is done with a single, consistent approach:
    addEventListener().
    For a newcomer, this is easier to learn because once the
    technique is
    understood, it works in nearly every scenario.
    As far as performance is concerned, AS3 trumps AS2
    significantly. AS3
    performs better and faster than all previous versions of
    ActionScript -- but
    you'll only notice this with complex applications, especially
    those
    involving a high volume of number crunching.
    Here are a few more links that may prove helpful to you:
    ActionScript 3.0 Overview
    http://www.adobe.com/devnet/actionscript/articles/actionscript3_overview.html
    Tips for Learning ActionScript 3.0
    http://www.adobe.com/devnet/actionscript/articles/actionscript_tips.html
    ActionScript 3.0: Is it Hard or Not?
    http://www.insideria.com/2008/01/actionscript-30-is-it-hard-or.html
    You also asked which version of the language has more "info
    and
    resources." By that, I assume you mean online resources, such
    as blogs,
    tutorials, and so on. That question is hard to answer, but my
    *guess* is
    that there are still more resources online about AS2 than AS3
    ... but AS3
    will probably catch up soon.
    David Stiller
    Co-author, Foundation Flash CS4 for Designers
    http://tinyurl.com/5j55cv
    "Luck is the residue of good design."

  • Full Access Permissions and AutoMapping in Exchange 2007?

    Hi,
    Using Exchange 2007 and Outlook 2010.  I have assigned Full Access Permissions to a mailbox but I don't know how to access that mailbox in Outlook.  Can anyone point me in the right direction?
    I see Exchange 2010 has a feature called automapping, which will load all mailboxes I have rights to in Outlook.  Is there a similar feature in Exchange 2007?  If not, what do I need to do in Outlook to access the other mailbox?
    Thanks in advance,
    Linn

    Not in Exchange 2007.
    You will have to add the mailbox manually:
    http://support.sherweb.com/Faqs/Show/how-to-add-another-persons-mailbox-to-your-outlook-2010-profile-exchange-2007
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Advantages and dis advantages of web dynpro java

    Hi Guys,
    May i know what are the advantages and dis advantages of web dynpro java?
    Regards,
    Madhu

    Hi Madhu,
    Web Dynpro (WD) is a proprietary web application user interface technology developed by SAP AG and exists in a Java (Web Dynpro for Java, WDJ or WD4J) and an ABAP (Web Dynpro ABAP[1]  , WDA) flavor. Both have in general the same functionality, but usually one flavor is improved after the other, so temporary one flavor is more advanced than the other. Hence, the decision for one of the two flavors shall be based on organizational and business circumstances, but not on functionality.
    WD follows an adapted MVC pattern and a model driven development approach ("minimize coding, maximize design") with a large number of dedicated hooks in generated code to place custom coding. It is intended for business applications that shall follow standardized UI principles, connect to backend systems and be scalable.
    Main advantages of Web Dynpro over other technologies
    typed access for design time checks, e.g. navigation links and messages are accessed via types instead of string keys like in JSF
    diverse services for backend access, like aRFC, JEE and Web Service data models
    integration with SAP Interactive Forms by Adobe, which are interactive PDF forms, during design (same IDE) and run time (data sharing)
    integration with business process management and business rules management (since NetWeaver CE 7.1 EHP 1)
    designed to support development big scale applications by adding multiple grouping layers on top of Java packages (DCs, SCs, products)
    runs on different clients e.g. web browser, mobile device, widget engine
    comes with a big collection of UI elements providing a wealth of functionality and only have to be configured but not programmed
    Main disadvantages
    proprietary, running only on SAP servers
    less flexible due to support for multiple clients (i.e. custom html is not possible). To reduce the limitations, several measures have been taken. For example, WD supports so-called "islands" for e.g. flash applications that enrich the Web Dynpro UI element collection by rich UI elements. This disadvantage doesn't seem so serious but in fact basic features that user expect to receive cannot be implemented (e.g. coloured rows in table, colours in general, advanced aligning of simple UI elements (due to nonexistence of more complicated ones), selecting multiple rows in tree-like tables (this is due to preserving basic concept of WD) and many more). Having the flash feature means that developer completely avoids WD UI (And thus cannot use other features).
    rendering speed in browser for larger tables (>1000 rows)
    The designtime and runtime environment is part of SAP NetWeaver 7.0[2] (also known as Netweaver 2004s) and following releases.
    The name comes after the original Dynpro library, whose name meant "Dynamic Program".
    Regards,
    Pradeep Kumar

  • What is the advantages and disadvantages of having 2012 DHCP within the Domain or its better to keep it stand alone

    What is the advantages and disadvantages of having 2012 DHCP within the Domain or its better to keep it stand alone
    I am Trying to upgrade Current DHCP 2003 Server to 2012 to get benefit from the latest fail over plan and I Want to be sure that it doesn’t affect the current setup

    Hi,
    For DHCP migration, there won’t be any problem. You can follow the guide below:
    Step-By-Step: Migration of DHCP from Windows Server 2003 to Windows Server 2012
    http://blogs.technet.com/b/canitpro/archive/2013/04/29/step-by-step-migration-of-dhcp-from-windows-server-2003-to-windows-server-2012.aspx
    If you have any other role installed on windows server 2003, please read the relevant article:
    Migrate Roles and Features to Windows Server 2012
    http://technet.microsoft.com/en-us/library/dn486809.aspx
    Hope this helps.

Maybe you are looking for