Conditional function for next/prev links in gallery

Has anyone written a function to conditionally show/hide the
next/prev
links?
Bryan Ashcraft (remove brain to reply)
Web Application Developer
Wright Medical Technologies, Inc.
=============================
Macromedia Certified Dreamweaver Developer
Adobe Community Expert (DW) ::
http://www.adobe.com/communities/experts/

Maybe that was poor phrasing. I'm wanting to the links only
when necessary.
I don't them to loop. In other words I only want the previous
button
available when there is a previous image. So it wouldn't show
on the first
image. The same with the next link.
Bryan Ashcraft (remove brain to reply)
Macromedia Certified Dreamweaver Developer
Paragon Visuals ::
http://www.paragonvisuals.com
Adobe Community Expert (DW) ::
http://www.macromedia.com/go/team/
~~~~~~~~~~~~~~~~~~~~~~~~
Got Questions? Get Answers
DWFAQ ::
http://www.dwfaq.com
PVII ::
http://www.projectseven.com/go/
"kinblas" <[email protected]> wrote in
message
news:e5ublf$kr4$[email protected]..
> Just curious ... why would you want to conditionally
hide them as opposed
> to just removing them? What would your condition be?
>
> --== Kin ==--

Similar Messages

  • PO requisition notifications page not showing NEXT/PREV links

    Hello All,
    In the PO Requisition Notifications page, the region containing all the lines "ReqLinesNotificationsRN" doesn't show any NEXT/PREV navigation links if the number of lines are more than the default value set at Profile - PO:%Notif%lines%disp%Limit%
    FYI,
    1. I've checked with Profile - PO:%Notif%lines%Disp%Limit% and found it 20 lines by default. I've tried removing this value and made it to NULL. Still no effect.
    2. Personalizing "ReqLinesNotificationsRN", which is a table region, I've set the option "records to be displayed" to 20. Still no effect
    Can somebody please inform how to find a solution to this?
    Thanks,
    Anand

    Most likely, the Status column has been inadvertently turned off or repositioned too far to the right for it to show in the panel. Drag the panel into an open area of your screen and drag out its right edge to make it wider. If you still don't see the Status column, choose Panel Options... from the panel menu and re-enable it by ticking its checkbox under Show Column.

  • Please Give me Idea for next , prev bt in specific case

    hi
    i have a movieclip with instance name : content
    in this movieclip i have Layer "slides"
    and in frame1 of this layer  i have movieclip called : content
    in the content movieclip i have various frames that i have some image , text , masks  ... like products and want to build something like slideshow !!
    now i want to Create Next , Previous Button to goto next and prev frames of my content ...
    i cant put my buttons in Content and i need to put these button in mc movie clip ( parent movieclip )
    So  i create new Layer and in frame 1 i create 2 buttons name : nextbt and prevbt and use these script :
    nextbt.addEventListener(MouseEvent.CLICK, fl_ClickToGoToNextFrame);
    function fl_ClickToGoToNextFrame(event:MouseEvent):void
        content.nextFrame();
    prevbt.addEventListener(MouseEvent.CLICK, fl_ClickToGoToNextFrame);
    function fl_ClickToGoToNextFrame(event:MouseEvent):void
        content.prevFrame();
    but now i have Problem :
    i dont want to show prevbt in first frame or Nextbt in last frames of content or i want to disable it on these frames ...
    thanks so much ...

    Use conditionals to set the visible property based on which frame the movieclip is in.  For instance...
    prevbt.visible = false;
    nextbt.addEventListener(MouseEvent.CLICK, fl_ClickToGoToNextFrame);
    function fl_ClickToGoToNextFrame(event:MouseEvent):void
         content.nextFrame();
         prevbt.visible = true;
         if(content.currentFrame == content.totalFrames){
            nextbt.visible = false;
    prevbt.addEventListener(MouseEvent.CLICK, fl_ClickToGoToNextFrame);
    function fl_ClickToGoToNextFrame(event:MouseEvent):void
        content.prevFrame();
         nextbt.visible = true;
         if(content.currentFrame == 1){
            prevbt.visible = false;

  • Jquery or code for Image loading on Sp Gridview Pager(Next ,Prev) click functionality on sharepoint 2010

    Jquery or dynamic code for Image loading on Sp Gridview Pager(Next ,Prev) click functionality on sharepoint 2010.
    i have a dynamic SP gridview contains Previous and next
    buttons for paging.
    page doesn't contain Update panel.
    grdXRPSUsers.PagerSettings.Mode = PagerButtons.NextPrevious;
    grdXRPSUsers.PagerSettings.PreviousPageText = "< Previous Page";
    grdXRPSUsers.PagerSettings.NextPageText = "Next Page >";
    grdXRPSUsers.PagerSettings.FirstPageText = "First Page";
    grdXRPSUsers.PagerSettings.LastPageText = "Last Page";
    When i click on Next or Previous page in the gridview it will take more time and showing progress bar in th below.
    As per my client request, i need to change the
    progress bar to Loading image (Wheel at middle of the grid at fething time).
    How its possible either through jquery or Programming(code behind).
    Please help

    Hi,
    According to your description, my understanding is that  you want to add loading image when click the paging button to load the data.
    I suggest you can use Jquery BlockUI Plugin to show a block image when loding data in paging click event.
    Here is a similiar thread for your reference:
    How to display a loading image until a gridview is fully loaded
    More information:
    Jquery BlockUI Plugin
    Thanks
    Best Regards
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • I'm trying to add prev and next button to a gallery

    I've found a free flash gallery which looks good for my need here: http://www.flashgallery.org/
    The only problem is that the gallery doesn't have prev and next buttons for the full size images, so I'm trying to add them.
    I've been able to add those buttons, but they only work if I don't click on a thumb, as I click on a thumb they stop working.
    In the code there is a function called loadGImage which loads the full size images, originally that function accepted 2 parameters, I've added a 3rd one which store the current image's index inside an array, so that I can use my buttons to call that function with index+1 for next and index-1 for prev.
    In addition to this I've added a variable which is updated everytime a full image is shown, that variable contains the image's index.
    Clicking on thumb the buttons stop working because the current image's index turns to "undefined" so they can't pass a correct value to loadGImage.
    I've checked the code of the gallery, but I can't find where is said to the thumbs to call loadGImage, if I'd found that code I could add the index parameter and my buttons would work.
    I'm sure that the thumbs call loadGImage because I've put a trace() inside the function to see when it is activated.
    Here you can find the source file of the gallery (plus some images to see how the gallery works)
    http://www.fileden.com/files/2008/4/9/1858524/FlashGallery2.rar
    The code commented using /*   */ is the code written by me.
    Can you help me to find where the thumbs make the call to loadGImage?

    The informations about the images are read from an XML file.
    These variables will contain the informations
    _root.description = new Array();
    _root.small_image = new Array();
    _root.big_image = new Array();
    _root.total_images = 0;
    This code creates the thumbs
    function createSmall()
        _root.smallContainer.createEmptyMovieClip("smallImageContainer", 10);
        var _loc4 = 0;
        var _loc3 = 0;
        for (var _loc2 = 0; _loc2 < _root.small_image.length; ++_loc2)
            _root.smallContainer.imageContainer.attachMovie("smallImage", "smallImage_" + _loc2, 100 + _loc2);
            m = _root.smallContainer.imageContainer["smallImage_" + _loc2];
            m._x = _loc3 * 50;
            m._y = 0;
            m.imageContainer.loadMovie(_root.small_image[_loc2], 100);
            m.iData = Array();
            m.iData.big = _root.big_image[_loc2];
            m.iData.title = _root.description[_loc2];
            ++_loc3;
        } // end of for
        _root.smallImageContainer._x = 5;
        _root.smallImageContainer._y = 0;
    } // End of the function
    And this is how full size images are loaded
    function loadGImage(title, bigImgURL)
        _root.bigImage.imageContainer.loadMovie(bigImgURL, 100);
        _root.bigImage.imageContainer._x = 0;
        _root.bigImage.imageContainer._y = 0;
        _root.title.text = title;
        //trace(bigImgURL);
    } // End of the function
    I've checked around the fla file, but I haven't found any code associated to the thumbs which says to call loadGImage, that's my problem, because the code itself is not hard to understand.

  • Partner functions for FV11 conditions are not working for MIRO

    Hi,
    We have a business process wherein PO Ordering vendor and invoicing vendor are different.
    We have defined  FV11  tax conditions  ( VAT and Excise)for PO vendor .
    We have not defined  FV11 tax conditions  ( VAT and Excise) for Invoicing vendor.
    So while we are doing MIRO for such PO, we are getting an error that  VAT tax code  say G1 is not maintained in TAXXINN proceedure.
    When we defined  TAX conditions for Invoicing vendor also ,  system allowed MIRO for such PO.
    We are using TAXINN proceedure.
    Guide  me whether :
    1. Definining VAT and Excise conditions for Invoicing vendor is a must ..?
    OR
    2. We can do some configuration in Partner functions  sothat whatever  Tax conditions defined for PO vendor will be defaulted and can be used sothat at the time of MIRO  there will not any error for VAT and Excise conditions defined only in PO.
    Thanks in advance !
    Thanks & Regds,
    Kasi.

    Hi  Kishore,
    Thanks a lot for quick  response .
    As you said we have defined FV condition records were defined to key combination specific to Vendor. Given the scenario, can we change partner functions from PI or VN or other related , will System allow defualt these conditions to invoicing partner..? Iam not very much sure how partner functions work..? can please throw some light on this or guide me a link where can I get information on partner functions?
    ALternatively , instead of defining FV11conditions for key combination with vendor, if we  define  FV 11 conditions for other combination such as at material group level- will it work?
    Thanks in advance.
    Thanks & Regds,
    Kasi.

  • Conditional option for Action link in OBIEE 11G

    Hi
    I am unable to select the conditional option for action links on a column(s) in 11g. Please help me with a solution to this or information on this.
    Thanks

    Hi,
    What error are you getting? Or the conditional option is invisible?
    Regards,
    Arul

  • Gallery problem with next/prev buttons

    Hi,
    I'm working on a photo gallery and I have some weird things
    happening, hence the request for help!
    When the gallery opens, you can click on any picture, the
    main one then appears with various buttons:
    1. Click on the image and you go back to the thumbnails -
    fine
    2. Click on the cross button and it's the same - fine
    3. Don't click on the automatic gallery, it's no on yet! :)
    4. Click on previous and the previous image appears - fine
    5. Click on next and the next image appears - nope, that's
    where the problem is!
    For the previous button, I use this code:
    var previous = "none";
    if (_global.currentImage == 1) {
    previous = _global.photoNum;
    } else {
    previous = _global.currentImage-1;
    _global.currentImage is the number related to the thumbnail
    you have clicked.
    _global.photoNum is the total number of pictures
    After this code, there's all the code for the preloader and
    it ends by defining the new current image (
    _global.currentImage = previous;) and loading it (
    mcLoader.loadClip("images/photo"+previous+".jpg",
    _level0.images_mc.holder_mc);).
    The next button is based on the same code:
    var next = "none";
    if (_global.currentImage == _global.photoNum) {
    next = 1;
    } else {
    next = _global.currentImage+1;
    With at the end
    _global.currentImage = next; and
    mcLoader.loadClip("images/photo"+next+".jpg",
    _level0.images_mc.holder_mc);.
    Here is the problem, there are three situation you use the
    next button:
    1. On the thumbnails, you click any image. When the main
    image is loaded, you click first previous, have the new image
    loaded and then you click next. The next image is loaded and it
    works fine.
    2. On the thumbnails, you click the last image. When the main
    image is loaded, you click next. The next image (which is then the
    1st) is loaded and it works fine.
    3. On the thumbnails, you click any image. When the main
    image is loaded, you click next.
    Here is the problem: the next image is not loaded!
    You can see it here:
    www.theminnesotafats.com/gallery
    When you see that the picture is not loaded, you will have to
    refresh the page to make it work again.
    I hope that those explainations are not too long and that
    somebody could help me. Thanks!

    WHEN 'NEXT'.
          PERFORM scroll_end.
    WHEN 'PREVIOUS'.
         PERFORM scroll_left.
    ENDCASE.
    ENDMODULE.                 " USER_COMMAND_7100  INPUT
    *&      Form  scroll_end
          text
         -->RT_COLUMNS text
    form scroll_end tables rt_columns type kkblo_t_columns.
      ENDFORM.
    *&      Form  scroll_left
          text
         -->RT_COLUMNS text
    form scroll_left tables rt_columns type kkblo_t_columns.
      ENDFORM.
    i've tried this....the previous error gone..but now i have another error said " the type kkblo_t_columns. is unknown ".
    really exhausting :P

  • Can't we use function to derive value for NEXT clause in MV ?

    Hi Friends,
    I have a requirement like below
    I need to derive the schedule (Value for NEXT clause in the create MV command) for a MV to run it
    e.g., Value from a date column : 03-JUL-2012 10:00 AM, VALUE for NEXT clause in CREATE MV statement should be 03-JUL-2012 04:45 AM (It is -5.45 hrs from the above date column value )
    So I wrote a function (GET_DATE) to derive schedule for NEXT clause and tried to call it from NEXT caluse, but it is giving error message as mentioned below
    ORA-04044: procedure, function, package, or type is not allowed here
    CREATE MATERIALIZED VIEW child_mv
    PARALLEL 16
    INITRANS 16
    STORAGE (
    FREELISTS 16
    FREELIST GROUPS 4
    BUILD IMMEDIATE
    REFRESH COMPLETE
    NEXT GET_DATE('PARENT_MV')
    AS
    SELECT * from xxmdme_party_stage where rownum<101;
    Could you please help to give some light on how this can be done ?

    942661 wrote:
    Hi Friends,
    I have a requirement like below
    I need to derive the schedule (Value for NEXT clause in the create MV command) for a MV to run it
    e.g., Value from a date column : 03-JUL-2012 10:00 AM, VALUE for NEXT clause in CREATE MV statement should be 03-JUL-2012 04:45 AM (It is -5.45 hrs from the above date column value )
    So I wrote a function (GET_DATE) to derive schedule for NEXT clause and tried to call it from NEXT caluse, but it is giving error message as mentioned below
    ORA-04044: procedure, function, package, or type is not allowed here
    CREATE MATERIALIZED VIEW child_mv
    PARALLEL 16
    INITRANS 16
    STORAGE (
    FREELISTS 16
    FREELIST GROUPS 4
    BUILD IMMEDIATE
    REFRESH COMPLETE
    NEXT GET_DATE('PARENT_MV')
    AS
    SELECT * from xxmdme_party_stage where rownum<101;
    Could you please help to give some light on how this can be done ?you must (ab)use EXECUTE IMMEDIATE

  • [svn] 4184: Fix for @ see tag referencing a non-global package function generates an empty link@ href in DITA

    Revision: 4184
    Author: [email protected]
    Date: 2008-11-25 12:33:43 -0800 (Tue, 25 Nov 2008)
    Log Message:
    Fix for @see tag referencing a non-global package function generates an empty link@href in DITA
    Also now the deprecated should show up in the property and method summary table.
    and when @see results in an invalid href, an additional attribute called invalidHRef will be added to the dita file - this isn't picked up by xslt but will be consumed by FB.
    QE Notes: Some baselines may need to be updated due to new attribute for invalidHRef
    Doc Notes: None
    Bugs: SDK-18206
    tests: checkintests
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-18206
    Modified Paths:
    flex/sdk/trunk/asdoc/templates/asdoc-util.xslt
    flex/sdk/trunk/asdoc/templates/class-files.xslt
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

    Update!
    v3.1 has a major bug! Even though it may appear to work properly, strange characters may leak onto the end of URLs, and you may even get segfaults. Sorry I didn't properly test it before releasing it!
    Technical details:
    I calloc()ed the memory for the link href improperly, per:
    link = calloc((noprepend ? 0 : urllen) + i - s, 1);
    Once I fixed it with "+ 1", per:
    link = calloc((noprepend ? 0 : urllen) + i - s + 1, 1);
    it worked great.
    I may use a method that doesn't use a calloc() in the future; this works for now, and I'm not gonna knock it...
    Last edited by dav7 (2009-01-23 12:38:51)

  • How to create menu function for link to open file

    Hi,
    I need help how to create menu function for link to access file and allow user to save the file when click on it.
    The file will keep inside server.
    Thank you.
    Regards,
    Wilson

    I need help how to create menu function for link to access file and allow user to save the file when click on it.
    The file will keep inside server.AFAIK, you have to write a custom code to achieve this and Oracle does not provide this functionality.
    If you want to store the file as an attachment, please see (How to Store Image/PDF Attachments on the File System in 11i and R12 (like Attachment File Directory) [ID 294525.1]).
    Thanks,
    Hussein

  • Suggest book on SAP HR Functional for beginners

    Dear All,
    Request you to suggest me a book for SAP HR Functional
    for beginners.
    Thanks in advance for the help.
    Regards,
    Taranjit

    Benefit Administration:
    This section of the Implementation Guide (IMG) is where you set the SAP Benefits Administration component.
    Here you enter in the system all the details of the benefit plans offered by your company.
    Benefit Area:
    Benefit areas allow you to have separate administration of different benefit plan pools. This division is primarily for administrational purposes and would not normally be used for eligibility
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Define Benefit Area
    Assign Currency to Benefit Area:
    In this step, you specify the currency for the benefit area
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Assign Currency
    this step, you enter the providers of the benefit plans you offer.
    This could be the Insurance company, or Health Maintenance Organization that receives the benefit plan costs
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Define Benefit Providers
    In this step, you set relevant benefit area for your Customizing activities
    If you have more than one benefit area to set up, you must set up each independently. After you have set up all the plans in one area, you must return to this view, set the next current benefit area and work through the IMG again, setting up the new benefit area.
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Set Current Benefit Area
    Benefit Plan Types:
    In this step, you enter the benefit plan types that you require for the plan categories predefined in the system.
    The following plan categories are provided by MSD:
    • Health Plans
    o Medical
    o Dental
    o Vision
    • Insurance Plans
    o Basic Life
    o Supplemental Life
    o Accidental Death & Dismember
    • Savings Plans
    o 403B
    o 457
    o PERS (Public Employees retirement Scheme for CP Benefit Plan) & TRS
    (Teachers Retirement Scheme for TP Benefit Plan)
    • Flexible Spending Accounts
    o Health care
    o Dependent care
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Plan Attributes &#61664; Define Benefit Plan Types
    Define Benefit Plan Status:
    It is important that you assigning statuses in order to be able to control the availability of plans with a minimum of effort. For example, you can control whether or not employees can enroll in a plan simply by changing its status
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Plan Attributes &#61664; Define Benefit Plan Status
    Benefit Plan Status:
    In this step, you define parameter groups. You decide which groups you require in two stages:
    1. You consider which costs, credits, coverage and employee and employer contributions for your plans vary according to the age, salary and/or seniority of employees (or possibly the age of the employee's spouse).
    2. You determine the different ways in which you need to divide your employees according to different value ranges for these criteria.
    It is not possible to define overlaps of ranges for a criterion within a single parameter group. Therefore, if you require different employee groupings for different plans, you need to create a separate parameter group.
    For each unique combination of criteria and their values, you need to define a parameter group.
    In this step, you simply create the parameter groups to which you assign groups for the individual criteria in the following steps. You later refer to the parameter groups, where applicable, in the individual rule variants for plans. Since one parameter group can be referenced by multiple plans, Customizing effort is kept to a minimum. In the plan variant, you also have the flexibility of being able to specify that you only want to use certain criteria values belonging to a parameter group, for example, age ranges
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; Define Employee Criteria Groups &#61664; Define Parameter Groups
    Age Groups:
    In this step, you define the age groups for the parameter groups that you defined in a previous step.
    Depending on your needs, you may find for some parameter groups, you can leave out this step, if for example there is no requirement to differentiate between employees based on age
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; Define Employee Criteria Groups &#61664; Define Age Groups
    Age Groups under Parameter grouping “PAR1”
    Cost Groupings:
    In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, job classification, marital status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying costs for different groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; Define Cost Groupings
    Coverage Groupings:
    In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, employment contract, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying coverage for different groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; Define Coverage Groupings
    Employee Contribution Groupings:
    In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; Define Employee Contribution Groupings
    the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; Define Employer Contribution Groupings
    the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; Define Employer Contribution Groupings
    the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; Define Options for Health Plans
    Dependent Coverage Options:
    In this step, you define the dependent coverage that are used in health plans.
    Define all possible variations that you need, because this view is not specific to any plan or plan option
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; Define Dependent Coverage Options
    Number of Dependents:
    In this step, you can restrict participation in a health plan under a dependent coverage option to certain types of dependent, as determined by the subtypes of the Family/Related Persons infotype (0021). You can also define a minimum and maximum number of persons of a particular type that can be covered. During enrollment, the system only includes those dependent coverage options in the benefit offer for which the appropriate dependents are available
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; Define Minimum and Maximum Number of Dependents
    Define Cost Variants:
    In this step you define cost variants to determine which factors influence the cost of a health plan for an employee. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual costs in this step. You simply define how costs vary according to:
    • Plan
    • Option
    • Dependent coverage
    • Employee data
    Before you start to define cost variants, you need to do the following:
    1. Determine how often costs vary for all the combinations of option and dependent coverage that you have defined in each plan.
    This indicates how many cost variants you need. You can use the same cost variant more than once, for example, if costs are always identical for the dependent coverages 'employee only' and 'employee plus family' within a plan, regardless of the plan option
    2. Determine how costs vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; Define Cost Variants
    Cost Rules:
    You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; Define Cost Rule
    Health Plan Attributes:
    In this step, you bring together all the definitions relevant to the health plan that you have made in the previous steps.
    You assign to each health plan:
    • Its options
    • Relevant dependent coverages
    • The cost variants for the combination of options and dependent coverages
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; Assign Health Plan Attributes
    Insurance Plans:
    In this step, you define general data for insurance plans
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Define Insurance Plan General Data
    Coverage Variants:
    In this step, you define coverage variants to determined which factors influence the coverage an employee is entitled to in a plan. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual coverage in this step. You simply define how coverage varies according to:
    • Plan
    • Coverage option
    • Employee data
    Before you start to define coverage variants, you need to do the following:
    1. Determine how often coverage varies for different coverage options.
    This indicates how many coverage variants you need. Note the following:
    • If a plan has set coverages (including salary multiples), you need a
    coverage variant for each.
    • If a plan allows employees to choose any amount of coverage within a
    range, you need only one coverage variant.
    • If a plan has options, you will need a coverage variant for each option.
    2. Determine how coverage varies according to employee data.
    This determines how you need to set up your variants using employee groupings. For each variant, you can specify a parameter group and coverage grouping to determine coverage
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664;
    Coverage Rules:
    In this step, you define the actual coverages for a plan.
    You need to define coverage for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
    Coverage can be defined as a flat amount or as a factor of salary
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Define Coverage Rules
    Cost Variants:
    In this step you define cost variants to determine which factors influence the cost of an insurance plan for an employee. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual costs in this step. You simply define how costs vary according to:
    • Plan
    • Coverage option
    • Employee data
    Before you start to define cost variants, you need to do the following:
    1. Determine how often cost varies for different coverage options:
    • If an insurance plan has set flat coverage options and flat costs, you need
    to define a cost variant for each flat cost.
    • If you have set flat coverage options and the flat costs are directly
    proportional to the coverage stated in the flat cost, you need only one
    cost variant.
    • If an employee can choose any amount of coverage within a range and the
    cost of the coverage is directly proportional to the coverage, you need
    only one cost variant.
    2. Determine how costs vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Define Cost Variants
    Cost Rules:
    You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Define Cost Rules
    Insurance Plan Attributes:
    In this step, you bring together all those parts of an insurance plan, that you have already defined in the previous few steps.
    You define the insurance plan options, then associate to each insurance plan:
    • Cost variant
    • Coverage variant
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Assign Insurance Plan Attributes
    Combined Coverage Limits:
    When you define coverages for plans such as insurance, you can set limits on the coverage amount. This is often used when the coverage is an amount dynamically calculated when the employee chooses her coverage.
    However these limits apply only to one plan and yet you might need to define limits which combine the coverages of more than one plan.
    In this chapter, you define these combined limits as follows:
    1. The limit that might span 2 or more plans is reduced to a mathematical equation, where there is an amount on one side and plan coverages on the other side. The two sides of this equation are then DIVIDED BETWEEN the two views in this chapter.
    2. The first view defines the limit in monetary terms which is one side of the equation. It also defines the operator (equals, is greater than, and so on).
    3. The second view defines the other side of the equation in terms of the plan coverages
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Combined Coverage &#61664; Combined Coverage
    Combined Coverage Limit Expressions:
    In this step, you enter the second half of the equation, as discussed in combined coverage
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Combined Coverage &#61664; Define Combined Coverage Limit Expressions
    Imputed Income for Selected Benefits:
    In this section of the IMG, you define the criteria needed to calculate Imputed Income.
    Imputed Income is based upon benefits paid for by the employer and calculated using rates set by the Internal Revenue Service (IRS). This value is then treated as taxable income for the employee
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Combined Coverage &#61664; Review Age Groups for Imputed Income
    Review Calculation Factors for Imputed Income:
    In this step, you check that the Imputed Income Rate Table entries are correct.
    The imputed income age groups are associated with the rates/factors set by the IRS
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Combined Coverage &#61664; Review Calculation Factors for Imputed Income
    Savings Plans:
    In this step, you define general data for savings plans.
    You have defined the relevant type, status, and provider for each plan in the Basic Settings section of the Benefits IMG
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; Define Savings Plan General Data
    Employee Contribution Variants:
    In this step you define employee contribution variants to determine which factors influence the permitted employee contribution to a plan. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual contributions in this step. You simply define how contributions vary according to:
    • Plan
    • Option (only for plans in the plan category Miscellaneous)
    • Employee data
    Before you start to define variants, you need to do the following:
    1. Determine how often employee contributions vary for plans and any plan options.
    This indicates how many contribution variants you need.
    2. Determine how employee contributions vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and employee contribution grouping to determine employee contribution
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; Define Employee Contribution Variants
    Employee Contribution Rules:
    In this step, you define the employee contribution limits for each plan.
    You need to define employee contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
    You can define minimum and maximum employee contribution in the following ways:
    • As a fixed amount
    • As a percentage of salary
    • As a contribution unit
    In Payroll, the total employee contribution is the sum of these amounts
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; Define Employee Contribution Rules
    Employer Contribution Variants:
    In this step you define employer contribution variants to determine which factors influence the contribution the employer makes to a plan. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual contribution in this step. You only define how contributions vary according to:
    • Plan
    • Option (only for plans in the plan category Miscellaneous)
    • Employee data
    Before you start to define variants, you need to do the following:
    1. Determine how often employee contributions vary for plans and any plan options.
    This indicates how many contribution variants you need.
    2. Determine how employee contributions vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and employer contribution grouping to determine employer contribution
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; Define Employer Contribution Variants
    Employer Contribution Rules:
    In this step, you define limits for the contributions made by the employer to employee plans. You so this for each employer contribution variant for each plan.
    You need to define employer contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
    You can define the employer contribution and the contribution limit in either of the following ways:
    • As a fixed amount / as an amount per unit contributed by the employee
    • As a percentage of employee base salary or employee contribution
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; Define Employer Contribution Rules
    Assign Savings Plan Attributes:
    In this step, you complete the definition of savings plans by bringing together the relevant elements that you have already defined:
    • EE contribution variant
    • ER contribution variant
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; Assign Savings Plan Attributes
    Flexible Spending Accounts (FSAs):
    In this step, you define general data for flexible spending accounts (FSAs).
    Requirements
    You have created the appropriate plan type , plan status, and benefit provider in the preceding steps
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Flexible Spending Accounts (FSAs) &#61664; Define Spending Account General Data
    Assign Spending Account Attributes:
    In this step, you enter the details of your flexible spending accounts including contribution limits, an employer contribution variant (if required), and rules for the reimbursement of claims
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Flexible Spending Accounts (FSAs) &#61664; Assign Spending Account Attributes
    Flexible Administration:
    In this chapter, you define the flexible aspects of your Benefits administration. You define the availability of plans to your employees, in terms of the plans themselves. You also define aspects of the enrollment process.
    you enter parameters that apply to processing within an entire benefits area, including:
    • Open enrollment period dates
    • Default validity dates for adjustment/standard plan records
    • Advance availability of future plans
    • Dependent age limits
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Define Administrative Parameters
    Benefit Adjustment Groupings:
    In this step, you define adjustment groupings. These groupings allow you to specify different adjustment permissions for different groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; Define Benefit Adjustment Groupings
    Benefit Adjustment Reasons:
    In this step, you define adjustment reasons to control changes to employee enrollments according to company policy.
    The adjustment reason types that you define here are assigned as subtypes of Adjustment Reasons records (infotype 0378) in HR Master Data. Since a record can only have one subtype, a new record must be created for every adjustment reason an employee experiences.
    According to the adjustment concept, an employee can only make changes to her enrollments if she has an Adjustment Reasons record (infotype 0378) with the required adjustment reason as a subtype. The only exceptions to this are if changes are made during an open enrollment period or if an anytime adjustment reason is assigned to the plan type.
    In addition to defining adjustment reasons for certain events that can trigger changes, you may also want to define a special adjustment reason to allow changes to plans at any time
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; Define Benefit Adjustment Reasons
    Adjustment Permissions:
    In this section, you assign adjustment permissions to each benefit plan type for an adjustment reason and any adjustment grouping that you have defined.
    Note that the elements for which you can define permissions are automatically determined by the system, dependent on the plan category
    Health Plans:
    In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; Define Adjustment Permissions &#61664; Health Plans
    this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; Define Adjustment Permissions &#61664; Insurance Plans
    Savings Plans:
    In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; Define Adjustment Permissions &#61664; Savings Plans
    Spending Accounts:
    In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; Define Adjustment Permissions &#61664; Spending Account
    Programs:
    In this section of the IMG, you define benefit programs and the eligibility restrictions and termination conditions for the plans within these programs.
    Within a program, eligibility for plans can be determined on two levels:
    • Program groupings control eligibility on a high level (macro-eligibility) by allocating an employee a defined program, depending on his/her organizational and employment data.
    • Eligibility rules are optional and control eligibility on a low level (micro-eligibility) by determining whether an employee can participate in a plan within the relevant program. An employee must fulfill the conditions defined in the rule in order to be able to enroll. Eligibility rules are assigned to plans in programs by means of an eligibility variant.
    First Program Grouping:
    In this step, you define first program groupings. Later, you define programs for a combination of first and second program groupings.
    Identical attributes are available for the setup of both the first and second program groupings, and they are therefore interchangeable. The fact that you determine macro-eligibility for a program using two dimensions means that you are able to make finer distinctions between groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Define First Program Grouping
    Second Program Grouping:
    In this step, you define second program groupings. Later, you define programs for a combination of first and second program groupings.
    Identical attributes are available for the setup of both the first and second program groupings, and they are therefore interchangeable. The fact that you determine macro-eligibility for a program using two dimensions means that you are able to make finer distinctions between groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Define Second Program Grouping
    Employee Eligibility:
    In this section of the IMG, you define the criteria according to which you control eligibility for individual benefit plans within a benefits program (definition of micro-eligibility). You perform the following steps to set up eligiblity requirements:
    • You define eligibility grouping to identify groups of employees for whom
    certain eligibility criteria apply.
    • You create eligibility variants, which you later use to link eligibility
    rules to programs.
    • If necessary, you define dynamic eligibility conditions relating
    specifically to actual hours worked/length of service, or zip codes.
    • You bring your definitions together in the eligibility rule, where you
    can also specify further conditions for enrollment.
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Employee Eligibility &#61664; Define Eligibility Groupings
    Eligibility Variants:
    In this step, you define eligibility variants. These consist simply of an identifier and a description
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Employee Eligibility &#61664; Define Eligibility Variants
    Eligibility Rules:
    In this step, you define eligibility rules for the benefit plans offered by your organization. You define these rules for combinations of eligibility grouping and eligibility variant, thereby determining the eligibility conditions that will apply for different groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Employee Eligibility &#61664; Define Eligibility Rules
    Participation Termination:
    In this section of the implementation guide you define criteria for the termination of benefit plans
    Termination Groupings:
    In this section of the implementation guide you define criteria for the termination of benefit plans
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Participation Termination &#61664; Define Termination Groupings
    Termination Variants:
    In this step, you define termination variants. These consist simply of an identifier and a description
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Participation Termination &#61664; Define Termination Variants
    Termination Rules:
    In this step, you define termination rules. You define these rules for every combination of termination grouping and termination variant, thereby determining the coverage continuation periods and termination day that will apply for different groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Participation Termination &#61664; Define Termination Rules
    Define Benefit Programs:
    In this step, you define termination rules. You define these rules for every combination of termination grouping and termination variant, thereby determining the coverage continuation periods and termination day that will apply for different groups of employees
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Define Benefit Programs
    Dependent/Beneficiary Eligibility:
    In this step, you define family member groupings and determine how family members are allocated to these groupings
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; Define Family Member Groupings
    Dependent Eligibility Rule Variants:
    In this step, you define the dependent eligibility variants to which you want to assign dependent eligibility rules. You also specify whether you wish to use a family member grouping in the associated eligibility rule to restrict eligibility to types of family members with certain characteristics
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; Define Dependent Eligibility Rule Variants
    Dependent Eligibility Rules:
    In this step, you define dependent eligibility rules to determine which types of family member are eligible as dependents. You then assign your rules to the appropriate plans by means of a rule variant in the step Assign Eligibility Rule Variant to Plan
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; Define Dependent Eligibility Rules
    Beneficiary Eligibility Rule Variants:
    In this step, you define the beneficiary eligibility variants to which you assign beneficiary eligibility rules in the next step. You also specify the following:
    • Whether you want to use a family member grouping in the associated eligibility rule to restrict eligibility to types of family members with certain characteristics
    • Whether the following apply for plans to which the variant is assigned:
    &#61607; The employee can be a beneficiary
    &#61607; Contingency beneficiaries can be named
    &#61607; Spouse approval is required if beneficiaries other than the spouse are to be amed (the system only takes this setting into consideration for plans of the category avings)
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; Define Beneficiary Eligibility Rule Variants
    Beneficiary Eligibility Rules:
    In this step, you define beneficiary eligibility rules to determine which types of family member are eligible as beneficiaries. You then assign your rules to the appropriate plans by means of a rule variant in the step Assign Eligibility Rule Variant to Plan
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; Define Beneficiary Eligibility Rules
    Assign Eligibility Rule Variant to Plan:
    In this step, you assign dependent eligibility variants and beneficiary eligibility variants to plans, thereby assigning the eligibility rules associated with these variants
    IMG Path: Personnel Management &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; Assign Eligibility Rule Variant to Plan
    COBRA Plans:
    In this step, you specify which health plans that you have already defined in the system are COBRA-relevant.
    When a clerk collects COBRA-qualified beneficiaries, the system only considers employee enrollments in the plans you select here as legitimate cases where COBRA must be offered to the employee
    IMG Path: Personnel Management &#61664; Benefits &#61664; COBRA &#61664; Choose COBRA Plans
    this step, you determine for which flexible spending accounts (FSAs) you will offer continuation of coverage under COBRA. You need to do this for each benefit area separately
    IMG Path: Personnel Management &#61664; Benefits &#61664; COBRA &#61664; Choose COBRA Spending Accounts
    Qualifying Event Coverage Periods:
    In this step, you define the events that qualify individuals for COBRA coverage, and the periods of permitted coverage continuation for each qualifying event type. COBRA legislation states the following regarding coverage continuation periods:
    • In the case of Termination of employment and Reduction in working hours, only 18 months coverage must be provided. If qualified beneficiaries are determined to be disabled within 60 days of the COBRA event, they are entitled to a further 11 months of coverage, as are the other qualified beneficiaries who experienced the original event.
    • For all other qualifying events except Bankruptcy of employer, a qualified beneficiary is entitled to 36 months continuation coverage, and there is no extension provision for disability.
    • In the case of the event Bankruptcy of employer, the coverage continuation period is the life of the retired employee or retired employee's widow/widower. You therefore do not need to define a continuation period in this case.
    IMG Path: Personnel Management &#61664; Benefits &#61664; COBRA &#61664; Define Qualifying Event Coverage Periods
    Assign COBRA Events to Personnel Actions:
    In this step, you define how the system recognizes COBRA-qualifying events from employee personnel actions (infotype 0000) records. You do this by creating a link between the two.
    The only COBRA-qualifying event types that you assign to personnel actions are:
    • Termination
    • Death of employee
    • Reduction in hours
    You need to assign these COBRA-qualifying event types since they are based on customizable entries in your HR master data and therefore cannot be delivered as standard.
    When the system collects COBRA-qualified beneficiaries, it considers employee records within the date range you specify in two stages as follows:
    1. The system searches for employee personnel action (infotype 0000) records. The COBRA qualifying events assigned to any personnel actions found are collected.
    2. The system checks other employee infotype records for specific information which corresponds to COBRA-qualifying event types
    IMG Path: Personnel Management &#61664; Benefits &#61664; COBRA &#61664; Assign COBRA Events to Personnel Actions
    Notification and Payment Intervals:
    In this step, you define details of COBRA administration for those states where state law concerning COBRA differs from federal law.
    Federal regulations are reflected in the state settings for the District of Columbia, which is also the system default.
    If you must comply with state regulations that differ from the federal regulations, you should create a new state entry. Otherwise, you can use the DC version for all employees, regardless of which state they reside in
    IMG Path: Personnel Management &#61664; Benefits &#61664; COBRA &#61664; Define Notification and Payment Intervals
    heck this one and let me know if there is anything else even arun has also given nice response so if u have any query pls revert back
    6

  • Button for next recording in the database

    Hello,
    I currently testing Adobe LiveCycle to create a PDF form with data link to a database (Access).
    The goal of my form is for the manager of each of our site to write variable about the paycheck of each employe. So first I create my AccessDatabase with a simple structure :
    N : Auto Number
    Matricule : Employe ID
    Nom : Name
    Prenom : First Name
    Service : Service (Accounting...)
    HeureMensuelBase : Contract hour information for the mouth
    HeureSemBase : Contract hour information for the week
    Mois : Mouth
    Annee : Year
    NbrHeureMensuelW : Write the number of hour the employe work this mouth
    NbrHeureSupp25pc : Extra hour paid 25% more
    NbrHeureSupp50pc : Extra hour paid 50% more
    NbrHeureSupp100pc : Extra hour paid 100% more
    NomPrime : Name of a special gratification
    MontantPrime : Amount of a special gratification
    So after, I create my ODBC connexion and insite AdobeLiveCycle, Data View, Create a connexion > Next > ODBC String connexion > SQL Request > SELECT * FROM Table_Access; > Next > Finish. Great I retreive all my fields. If I preview the PDF I can correctly see the first record of my database.
    My goal is to create two differents buttons to navigate inside :
    NEXT with the follow code :
    formulaire1.#subform[0].Next::click - (JavaScript, client)
    xfa.sourceSet.DataConnection.next();
    PREV with the follow code :
    formulaire1.#subform[0].Prev::click - (JavaScript, client)
    xfa.sourceSet.DataConnection.previous();
    If i try to preview it, unfortunatly no button works.
    I follow this video : http://www.youtube.com/watch?v=C56_Cz-aE0c
    I  see the Adobe FAQ too : http://help.adobe.com/en_US/livecycle/11.0/DesignerHelp/WS107c29ade9134a2c-1f4d3e3c12a7df3 f73e-8000.2.html
    Could help me ? Adobe Support don't want help me because I use a trial version for the moment (logical because my CTO wan't valide LiveCycle do the job before paid for it). Sorry for my english it's not my mother tongue.

    I'm not alone in the same situation : http://forums.adobe.com/thread/793214
    Please support help us

  • ABAP Routines & Condition Types for SD Transactions

    Hi All,
    Is there any documentation available online aout how to create routines and condition typed for standard SD transactions?
    I have done some and I am actually looking for the following:
    In TCODE: VF04, after entering the start date & end date (p_fkdat & p_fkdab), on selecting a record from the displayed report and clicking on simulation, I need to know the start & end dates are stored and exported to the next TCODE in sequence (VF01).
    That's it. Will wait to see some replies.
    Regards,
    Karthik

    See the link below. Its a nice doc for VOFM
    www.saptechsolutions.com/ pdf/VOFMCopyRequirementRoutines.pdf
    Cheers,
    Thomas.

  • Stories Limitation? - Unable to use Next/Prev Jump with individual Stories.

    I have tried to use Stories on a recent DVD project to save scripting a 'Play All' button. From reading many people have advised using Stories for this particular reason. However I have run into one issue which I can't get around:
    When selecting an individual story to play I can't find a way to allow the user to 'Next Jump' or 'Prev Jump'. This only seems possible if the whole track is selected as if the user presses 'Play All' - then the user can Next Jump / Prev Jump to the following or previous track.
    What I want to do is allow the user the option to simply Next / Prev Jump when playing an individual story so they can return to the menu instead of pressing the menu button. Is this a limitation with Stories? I have read other people having a similar problem but would like confirmation if anyone knows. Thank you.

    hangmanstudios wrote:
    What I want to do is allow the user the option to simply Next / Prev Jump when playing an individual story so they can return to the menu instead of pressing the menu button.
    Argh.... sorry when I read these parts of the original post I thought you were referring to the next/previous in a story that would not work and you had to wait for the story to end or break out with the menu command. The link you later referred to, well then I got it. You want to jump between stories.
    There are various ways to try to do things but there is no way to assign the story to end jump two different ways (sort of) based on whether the prev/next command is pressed. In other words if you have a menu that has a story to play Scene 2 of a movie, you can arrange things so that when Scene 2 is over you can either go back to the Menu OR go to another story. If you want to point people into an entire movie and start at a Scene you can point to a "Play All" story and the Chapter Marker in the Play All story and it will prev/next. If the story jumps to a story on another track, you can try to script previous next to work, but then again it is only in the context of having some decisions made as to how you want it to navigate, but it may not be perfect...not sure if that makes sense(?)

Maybe you are looking for

  • N81 is not getting started.

    my mobile n81 has some problem as while charging it give only white li8 and it is not getting on after a long time of chargin. can u tell wht is the problem in it and how can it be ressolved????????????

  • 24" display versus 27"

    I have a macbook pro from 2009. I am looking to purchase a monitor and can't decide between getting a used LED Cinema Display 24 inch LCD and a new LED Cinema Display (27" flat panel). 1. Besides the size (and price) what are the differences as far a

  • Certain websites media player wont work after installing Firefox V4

    After installing Firefox Version 4 the media player of certain website fails to start and stream normally. I have updated all the needed plugins and add ons and still have the same issue. I have created a Mozilla account and downloaded Spark and my S

  • Audio in Advance Action Doesn't Execute from "On Success" in Quiz Question

    In each of my quiz slides, I have set the On Success action to Execute an Advanced Action.  In the Advanced Action, I have two lines.  The first line is to run audio that says something like "That's Correct - great work - click any key to continue" a

  • My macbook froze and won't reboot

    I was using the RGB cable with the VGA adaptor to show a movie and my macbook froze in the process. I had to hold the power button down to get it to turn off, but when I pressed it again to reboot, all I my macbook does is that sound it does when it'